domain: caprover.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
npm install -g caprover, then run caprover serversetup (first-time) or caprover login to authenticate against your Captain instance
Add a captain-definition JSON file (schemaVersion: 2, plus templateId, dockerfilePath, or imageName) at the root of your project
Run caprover deploy and answer the interactive prompts to select app and branch
Use caprover deploy -d to reuse previously entered values for the current directory without prompts
For CI/CD, run non-interactively: caprover deploy -u <url> -p <password> -b <branch> -a <app-name> (-u/--caproverUrl; or use --appToken instead of a password)
Known gotchas
captain-definition must sit next to package.json, index.php, etc. at the project root — CapRover looks for it there by default
Deploys from a git branch only include committed, non-gitignored files — uncommitted changes are silently excluded
--appToken provides app-scoped authentication as an alternative to the account password, useful for locking down CI credentials
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?