Getting Started
Deploy your first application
Connect a repository, choose deployment stages, configure each release path and follow the first deployments.
Before you start
Have these details ready before opening the deployment form.
- A workspace with an active package that allows another application.
- A GitHub repository you can access, or the URL of a public repository.
- The branches that should supply Development, Testing, Staging and Production.
- The environment values, database choice and application port required by each enabled stage.
Start in the workspace where this application should live.
Open Deploy ApplicationView Applications1. Choose and inspect the source repository
- 1Select Private or Public repository access.
- 2Choose the repository and initial branch.
- 3Wait for source detection to finish.
- 4Review the detected stack, framework, version, project directory and build commands against the repository documentation.
2. Choose deployment stages
Branch-Based Deployment lets every enabled stage follow its own branch. Manual Promotion keeps one shared branch and allows automatic deployment only on the first enabled stage; later releases are promoted deliberately.
- 1Enable only the stages the application needs. Production is always included.
- 2Choose Branch-Based Deployment or Manual Promotion.
- 3For branch-based deployment, select the branch and automatic-deployment preference for every stage.
- 4For manual promotion, review the shared branch and confirm that only the first stage watches for source changes.
3. Configure stage resources
- 1Review environment variables and keep secrets out of source control.
- 2Choose whether the stage creates a database, uses an existing database or runs without one.
- 3Confirm the internal application port and build commands.
- 4Keep the generated Ghost Deploy address; attach customer domains to Production unless another stage intentionally needs public traffic.
4. Deploy and verify every enabled stage
- 1Select Deploy Application once.
- 2Open the application and review each stage separately.
- 3Wait for every intended stage to report Running.
- 4Open each stage address and test its actual application and database connection.
- 5Confirm automatic deployment only on the stages where it was enabled.
If something does not work
- A branch is missing: review GitHub repository permissions and refresh the connection.
- A later Manual Promotion stage deploys automatically: disable its automatic deployment and keep it enabled only on the first stage.
- Environment values differ unexpectedly: open the intended stage before editing and verify the stage name in the header.
- Build succeeds but the stage does not open: confirm the start command listens on 0.0.0.0 and the configured port.
- Database copy or storage copy is requested: review the destructive replacement warning and create a backup before replacing target data.