← All guides

Deployment guide

Take source code to a verified AnchorScape release

Use this path for a new codebase that should run on AnchorScape. The platform can detect recognised stacks and generate containerisation when the repository does not already provide it.

Result: A tested development deployment that can be promoted to staging and production.

Before you deploy

  • Connect GitHub in Settings for private repositories.
  • Create the dev environment first if required secrets or a database must exist before startup.
  • Make the application listen on 0.0.0.0 and the platform-provided port.
  • Keep development/test tools out of the production runtime unless they are genuinely runtime dependencies.

Deploy

  1. 1Open Console → Deployments → Deploy a system to AnchorScape.
  2. 2Choose connected GitHub, a public Git URL or a ZIP.
  3. 3Select dev. Production is never the implicit first destination.
  4. 4Watch build, rollout and verification in the deployment detail.
  5. 5If the build fails, check stack detection, the lockfile, runtime version, build command and private package credentials.
  6. 6If health fails, check that the app answers the configured health path without authentication.

Promote

After dev verification, manage staging and production from Environments. Promotion preserves the built image and release evidence, avoiding “same source, different build” drift.

Need help on the screen?

Open Anchorton and ask where a setting belongs. For runtime questions, open it from the deployment context so it can use the permitted status, event and log tools.