Add analytics to list of required domains for Enterprise QuickStart#464
Add analytics to list of required domains for Enterprise QuickStart#464jpshackelford wants to merge 1 commit intomainfrom
Conversation
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>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
all-hands-bot
left a comment
There was a problem hiding this comment.
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` | |
There was a problem hiding this comment.
🟡 Suggestion: Consider placing analytics.<your-domain> before llm-proxy.<your-domain> for alphabetical consistency:
| | `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.
|
@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. |
Summary
Add
analytics.<your-domain>to the list of required DNS domains for OpenHands Enterprise QuickStart, following the same pattern asllm-proxy.Changes
analytics.<your-domain>to the DNS A records table in the Manual VM Setup sectionanalytics.${BASE_DOMAIN}to the DNS test script in the Preflight Validation sectionThis PR was created by an AI assistant (OpenHands) on behalf of the user.
@jpshackelford can click here to continue refining the PR