docs: add self-host cloud guides and blog post#2766
Conversation
Add a blog post on deploying LLM Gateway on cloud platforms, restructure the docs Self Host section into a card landing page with Docker, Docker Compose, Kubernetes, AWS, GCP, and Azure guides, and add an Infrastructure-as-Code section to the enterprise page. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
WalkthroughRemoves the monolithic ChangesSelf-host documentation restructure
InfrastructureAsCodeEnterprise UI section
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 77%, saving 1.3 MB.
|
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 12.5%, saving 48.2 KB.
|
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 12%, saving 40.5 KB.
|
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 10.5%, saving 31.4 KB.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6dbc1a8d97
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Provide a `values.yaml` to point the chart at your managed database and cache and to set your secrets: | ||
|
|
||
| ```yaml | ||
| config: |
There was a problem hiding this comment.
For users following this Kubernetes guide (and the linked cloud guides), the sample values.yaml is placed under a top-level config key, but the chart never reads .Values.config; it renders database/auth/provider settings from auth.*, postgresql.enabled/externalPostgresql.*, redis.enabled/externalRedis.*, and llmProviders.* in infra/helm/llmgateway/values.yaml and templates/secret.yaml. As written, these managed DB/cache endpoints, auth secrets, and provider keys have no effect, so the release keeps the built-in stores/default secrets instead of the intended production configuration.
Useful? React with 👍 / 👎.
| ```yaml | ||
| config: | ||
| DATABASE_URL: "postgres://user:password@your-postgres-host:5432/llmgateway" | ||
| REDIS_URL: "redis://your-redis-host:6380" |
There was a problem hiding this comment.
This Azure example points Redis at port 6380, which Azure documents as the TLS endpoint, but the app's Redis clients only pass host/port/password to ioredis and the Helm values expose no TLS option. In an Azure Cache for Redis deployment that keeps the default TLS-only access, the API/gateway/worker/auth Redis connections will fail; the guide should either require a supported non-TLS endpoint/port or document/add TLS-capable Redis configuration.
Useful? React with 👍 / 👎.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (2)
apps/ui/src/content/blog/2026-06-20-deploy-llmgateway-on-cloud-platforms.md (2)
39-43: 💤 Low valueMinor: Consider tightening line 43 by removing or replacing "exactly".
The word "exactly" in "which is exactly what a managed database gives you" is slightly filler and is flagged as overused. Either remove it or use a more precise alternative:
- Remove: "which is what a managed database gives you."
- Replace: "which is precisely what a managed database gives you." (though "exactly" and "precisely" have similar overuse concerns)
- Rephrase: "and managed databases deliver all of these."
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@apps/ui/src/content/blog/2026-06-20-deploy-llmgateway-on-cloud-platforms.md` around lines 39 - 43, In the blog post's "How the pieces fit together" section, the word "exactly" appears in the phrase "which is exactly what a managed database gives you" at the end of the last paragraph. This word is identified as filler and adds unnecessary verbosity. Remove the word "exactly" from this phrase to tighten the writing and improve clarity, resulting in "which is what a managed database gives you." Alternatively, consider rephrasing the entire clause to something more direct like "and managed databases deliver all of these" if you prefer a more substantial revision.Source: Linters/SAST tools
76-78: 💤 Low valueMinor: Reduce repetitive opening phrase in the cloud guides list.
The three bullet points (lines 76–78) all start with "- [Deploy on", which creates a monotonous rhythm. Consider varying the first cloud's phrasing or restructuring to improve readability:
Current:
- [**Deploy on AWS**](...) — EKS, RDS, ElastiCache, and Secrets Manager. - [**Deploy on Google Cloud**](...) — GKE, Cloud SQL, Memorystore, and Secret Manager. - [**Deploy on Azure**](...) — AKS, Azure Database for PostgreSQL, Azure Cache for Redis, and Key Vault.Suggested alternative:
- [**AWS**](...) — EKS, RDS, ElastiCache, and Secrets Manager. - [**Google Cloud**](...) — GKE, Cloud SQL, Memorystore, and Secret Manager. - [**Azure**](...) — AKS, Azure Database for PostgreSQL, Azure Cache for Redis, and Key Vault.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@apps/ui/src/content/blog/2026-06-20-deploy-llmgateway-on-cloud-platforms.md` around lines 76 - 78, The three cloud deployment bullet points at lines 76-78 have repetitive opening phrasing with "- [**Deploy on" repeated identically for AWS, Google Cloud, and Azure. To improve readability and reduce monotony, simplify the link text by removing the "Deploy on" prefix from each of the three links, keeping only the cloud provider names (AWS, Google Cloud, Azure) as the link text while maintaining all the URLs and the service information that follows the em-dash unchanged.Source: Linters/SAST tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@apps/ui/src/content/blog/2026-06-20-deploy-llmgateway-on-cloud-platforms.md`:
- Around line 39-43: In the blog post's "How the pieces fit together" section,
the word "exactly" appears in the phrase "which is exactly what a managed
database gives you" at the end of the last paragraph. This word is identified as
filler and adds unnecessary verbosity. Remove the word "exactly" from this
phrase to tighten the writing and improve clarity, resulting in "which is what a
managed database gives you." Alternatively, consider rephrasing the entire
clause to something more direct like "and managed databases deliver all of
these" if you prefer a more substantial revision.
- Around line 76-78: The three cloud deployment bullet points at lines 76-78
have repetitive opening phrasing with "- [**Deploy on" repeated identically for
AWS, Google Cloud, and Azure. To improve readability and reduce monotony,
simplify the link text by removing the "Deploy on" prefix from each of the three
links, keeping only the cloud provider names (AWS, Google Cloud, Azure) as the
link text while maintaining all the URLs and the service information that
follows the em-dash unchanged.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 268f2e4d-bf23-470c-a541-2611edf8467b
⛔ Files ignored due to path filters (1)
apps/ui/public/blog/deploy-llmgateway-on-cloud-platforms.pngis excluded by!**/*.png
📒 Files selected for processing (13)
apps/docs/components/self-host-cards.tsxapps/docs/content/self-host.mdxapps/docs/content/self-host/aws.mdxapps/docs/content/self-host/azure.mdxapps/docs/content/self-host/docker-compose.mdxapps/docs/content/self-host/docker.mdxapps/docs/content/self-host/gcp.mdxapps/docs/content/self-host/index.mdxapps/docs/content/self-host/kubernetes.mdxapps/docs/content/self-host/meta.jsonapps/ui/src/app/enterprise/page.tsxapps/ui/src/components/enterprise/iac.tsxapps/ui/src/content/blog/2026-06-20-deploy-llmgateway-on-cloud-platforms.md
💤 Files with no reviewable changes (1)
- apps/docs/content/self-host.mdx
1 participant
Summary
Adds a blog post on deploying LLM Gateway on cloud platforms, restructures the docs Self Host section into a card-based landing page with per-target guides, and adds an Infrastructure-as-Code section to the enterprise page.
Blog (apps/ui)
gpt-image-2(1536×1024), text-free.Docs Self Host section (apps/docs)
Converts the single
self-host.mdxinto an expandable folder under the Self Host tab:index.mdx— landing page using a newSelfHostCardscomponent, grouped into Single host (Docker, Docker Compose) and Cloud (Kubernetes/Helm, AWS, GCP, Azure), styled to match the Introduction page cards.docker.mdx,docker-compose.mdx,kubernetes.mdx— single container, multi-container, and Helm chart deep-dive.aws.mdx,gcp.mdx,azure.mdx— what to configure per cloud (managed Postgres, Redis, compute/k8s, networking, secrets) plus the Helm deploy. Each has a Terraform/IaC enterprise callout at the top and bottom linking to/enterprise.Enterprise page (apps/ui)
InfrastructureAsCodeEnterprisesection ("Deploy your whole stack in one command") between pricing and open-source, pitching the Terraform modules with a/enterprise#contactCTA.Verification
pnpm formatand thedocsbuild pass; blog passes content-collections schema validation.gpt-tokenizermodule-resolution error inapps/ui(untouched by this PR).🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Documentation