Update deployments section + hosting for app deployment control plane #1106
Conversation
katmayb
force-pushed
the
sh-hosting-deployment
branch
from
5b98651 to
3f5fd63
Compare
|
Preview ID generated: preview-shhost-1761330983-0823b76 |
|
Preview ID generated: preview-shhost-1761577978-08b3d1d |
| ] | ||
| }, | ||
| { | ||
| "group": "Deploy to self-hosted or hybrid", |
There was a problem hiding this comment.
General suggestion/feedback, not specific to this change: It is unintuitive to me that the "deploy" sections are listed before the "development" and "configure" sections, which are prerequisites to deployment. My ordering preference:
- Overview (includes Quickstart so you get skip ahead to getting the app running)
- App development (read this first so you understand conceptually what you're about to deploy)
- Configure for deployment (read this second so you understand how to configure the deployment)
- Deploy to cloud (do the deployment)
- Deploy to self-hosted or hybrid
There was a problem hiding this comment.
Separate idea (not blocking): It feels like the "deploy" sections can be consolidated under one navigation header, but maybe it's still different enough to have different sections.
We can come back to this later.
There was a problem hiding this comment.
I'm going to leave this for now and have Kathryn address the nav order / consolidation when she's back. Filed an issue for her: https://linear.app/langchain/issue/DOC-408/rearrange-langsmith-nav
| Push your image to a container registry accessible by your Kubernetes cluster. The specific commands depend on your registry provider. | ||
|
|
||
| <Tip> | ||
| Tag your images with version information (e.g., `my-registry.com/my-app:v1.0.0`) to make rollbacks easier. |
|
Preview ID generated: preview-shhost-1761665890-d433a4b |
|
Preview ID generated: preview-shhost-1761666130-983694a |
Fixes DOC-398, DOC-399
It was a little confusing to find app deployment instructions for self-hosted and Hybrid instances. The Deployment tab only covered Cloud (GitHub-based) deployments.
This PR creates clear separation between infrastructure setup (one-time) and application deployment (ongoing):
New file:
Updated files: