Skip to content

Add analytics to list of required domains for Enterprise QuickStart#464

Open
jpshackelford wants to merge 1 commit intomainfrom
add-analytics-domain
Open

Add analytics to list of required domains for Enterprise QuickStart#464
jpshackelford wants to merge 1 commit intomainfrom
add-analytics-domain

Conversation

@jpshackelford
Copy link
Copy Markdown
Contributor

Summary

Add analytics.<your-domain> to the list of required DNS domains for OpenHands Enterprise QuickStart, following the same pattern as llm-proxy.

Changes

  • Added analytics.<your-domain> to the DNS A records table in the Manual VM Setup section
  • Added analytics.${BASE_DOMAIN} to the DNS test script in the Preflight Validation section

This PR was created by an AI assistant (OpenHands) on behalf of the user.

@jpshackelford can click here to continue refining the PR

Add analytics.<your-domain> to the DNS A records table and DNS test script,
following the same pattern as llm-proxy.

Co-authored-by: openhands <openhands@all-hands.dev>
@mintlify
Copy link
Copy Markdown

mintlify Bot commented Apr 21, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
all-hands-ai 🟢 Ready View Preview Apr 21, 2026, 12:19 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Copy link
Copy Markdown
Contributor

@all-hands-bot all-hands-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clean documentation update that follows the existing pattern. One minor ordering suggestion below, but not blocking.

| `app.<your-domain>` | `app.openhands.example.com` |
| `auth.app.<your-domain>` | `auth.app.openhands.example.com` |
| `llm-proxy.<your-domain>` | `llm-proxy.openhands.example.com` |
| `analytics.<your-domain>` | `analytics.openhands.example.com` |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Suggestion: Consider placing analytics.<your-domain> before llm-proxy.<your-domain> for alphabetical consistency:

Suggested change
| `analytics.<your-domain>` | `analytics.openhands.example.com` |
| `analytics.<your-domain>` | `analytics.openhands.example.com` |
| `llm-proxy.<your-domain>` | `llm-proxy.openhands.example.com` |

Alternatively, if there's a logical grouping reason (deployment order, functional grouping, etc.), that's fine too. This is a minor style preference.

@jpshackelford
Copy link
Copy Markdown
Contributor Author

@aivong-openhands @jlav I'll let you guys handle the PRs for OpenHands-Cloud, etc. but I wanted you to know we had @neubig's blessing on this domain name for the Laminar stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants