← All guides

Drydock guide

Build in a persistent browser workspace, then deploy through policy

Drydock is the isolated development workspace: files, terminal and preview. It is intentionally separate from the production deployment runtime.

Result: Tested source in a persistent workspace that can be handed to the normal AnchorScape build and verification path.

Create and work

  1. 1Open Drydock and create an empty workspace or import a GitHub repository.
  2. 2Connect GitHub in Settings before importing private source.
  3. 3Wait until the workspace is Running, then use the file tree, editor and terminal.
  4. 4Run tests, start a supported dev server command and open Preview.
  5. 5Stop when idle. Stop retains workspace storage; Delete permanently removes it.
  6. 6Use Deploy to pass source into the AnchorScape deployment process.

Why it does not deploy straight from the shell

The development workspace can contain test tools and mutable state. Production receives a fresh build with production dependency handling, policy enforcement, release evidence and post-deploy verification.

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.