Repository navigation
docs: add migration guide from Ona (formerly Gitpod) to Coder - #31204
Merged
Merged
Conversation
Contributor
Docs previewCheck off each page once it's been reviewed. If a page changes in a later push, its checkbox clears automatically so it gets a fresh look. Pages not yet wired into the docs navigation aren't listed here. |
david-fraley
removed their request for review
November 4, 2026 15:42
Collaborator
|
Spoke with @nickvigilante; removing myself as a reviewer. Nick will handle any follow ups. |
nickvigilante
force-pushed
the
docs/migrate-from-ona
branch
from
November 5, 2026 18:20
2ce8af4 to
0302d04
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Generated by Coder Agents on behalf of @nickvigilante.
Adds a migration guide for platform engineers moving an Ona (formerly Gitpod) Enterprise deployment to a self-hosted Coder deployment. Tracks DOCS-1415.
@david-fraley @nickvigilante, this is a first draft for review.
What the guide assumes
It's written for a typical enterprise Ona setup: Ona-hosted management plane, AWS or GCP runners in the customer's VPC, OIDC SSO with SCIM, groups and org roles, projects with
devcontainer.jsonand.ona/config.yaml, org/project/user secrets, daily prebuilds with a service-account executor, org policies (auto-stop, max lifetime, archive/auto-delete, port sharing, security agents, deny lists), Codex Agent with Ona Intelligence or BYOK, MCP integrations, and Automations triggered by PRs, schedules, and webhooks.How it converts
devcontainer.json: Dev Containers integration (VM templates) or Envbuilder (Kubernetes).ona/config.yamltriggers: dev container lifecycle commands,coder_script, andcoder_appVerification
mainat 78aa570.coder/registry.make docs/manifest.json,pnpm run format-docs,pnpm run check-docs, and Vale all pass.Open questions for review
docs/install/plan/migrate-from-ona.mdunder Install > Plan your deployment. DOCS-1414 will decide whether competitor migration guides get their own sidebar group.state, since the guide mixes OSS and Premium steps.Rebase onto main (conflict resolution)
mainat 585485c.docs/manifest/tutorials.ymlanddocs/tutorials/no longer exist, so the page moved to Install > Plan your deployment, after Sizing.docs/redirects.json(admin/templatestotemplates,ai-coder/*tocoder-agentsandai-governance,user-guidestoworkspaces, and the old Tutorials pages to their new sections). The prose is unchanged.docs/manifest.jsonwithmake gen/docs-manifest.pnpm run check-docs,make lint/docs-manifest,make lint/docs-redirects, and the pre-commit hook pass, and every link and anchor resolves.AbbreviationFirstUseandStepLengthwarnings, which are advisory only.