Repository navigation
Conversation
Add 'Arcade Deploy on your own cluster (Helm)' under Operate > Deploy, covering prerequisites, deployments.* chart values, the engine-level resource request keys from monorepo #5306 (not yet exposed by the chart), deploying, status and logs, upgrades, and troubleshooting. Unverified items are marked with TODO comments. Fix build/arcade-deploy and the deploy overview so they say Arcade Deploy also runs in a self-hosted installation, and link the new guide from the Helm page. Refs DEP-371, DEP-365
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changed and why
Adds an operator guide for turning on Arcade Deploy in a self-hosted Arcade installation, and points the existing developer and deploy pages at it.
DEP-371 (umbrella DEP-365).
app/en/operate/deploy/helm-arcade-deploy/page.mdx: Arcade Deploy on your own cluster (Helm).app/en/operate/deploy/_meta.tsx.app/en/build/arcade-deploy/page.mdx: the info callout now says Arcade Deploy can run on Arcade Cloud or in a self-hosted installation, and a second callout points developers atarcade login --urlplus the new operator page.This stays a draft until the 19
TODOMDX comments are verified. They mark behavior that is not confirmed yet (chart minimum version, credential handoff, quota interaction, runner tag behavior, and the self-hostedarcade login/arcade deploypath). Leave those comments in. Do not mark this ready for review until they are resolved.Preflight
Head
8d55deccf0539bfe44c3c4ad7db58000a18d7c21. No content changes during preflight.pnpm installpnpm buildpnpm lintpnpm typecheckpnpm testpnpm check-metaLocal verify
Production server:
pnpm start(next start) athttp://127.0.0.1:3000.curl -sIon the new page and the edited Arcade Deploy page both returnedHTTP/1.1 200 OK. Page titles:/en/operate/deploy/helm-arcade-deploy—Arcade Deploy on your own cluster (Helm) | Arcade Docs/en/build/arcade-deploy—Cloud deployments with Arcade Deploy | Arcade DocsLocale-less paths redirect and resolve. Nav entry on
/en/operate/deployishref="/en/operate/deploy/helm-arcade-deploy"with the label Arcade Deploy on your own cluster (Helm). Changed links (Helm guide, Arcade Deploy guide, CLI cheat sheet, MCP Gateways, platform architecture, Helm#upgrade-and-roll-back) return 200. The table and upgrade sentences from8d55deccare in the rendered HTML.Proof:
/opt/cursor/artifacts/dep-371-local-verify.txtProof footer
8d55deccf0539bfe44c3c4ad7db58000a18d7c21