Deployments
The Deployments section shows every time your app has been deployed. Each deployment is a complete cycle: Galaxy takes your code, builds it, and gets it running on containers.
Deployment History
The deployment history table shows every deployment your app has had. Each row shows:
| Column | Description |
|---|---|
| Status | Success, Failed, In Progress, or Cancelled |
| Version | Which version of your code was deployed |
| Source | The Git branch and commit hash |
| Trigger | What initiated this deployment |
| Triggered By | Who or what triggered the deployment |
| Started | When this deployment began |
| Duration | How long the deployment took |
Click any deployment to see details: build logs, deploy logs, timing information, and what happened at each stage.
Deployment Triggers
The Trigger column tells you how a deployment was initiated. Galaxy tracks five trigger types:
| Trigger | What It Means |
|---|---|
| Manual | Someone clicked "Deploy Now" or "Deploy with Custom Configuration" in the dashboard |
| Webhook | A push event from GitHub triggered automatic deployment |
| API | Deployment via CLI (galaxy deploy) or programmatic API calls |
| Rollback | Someone rolled back to a previous version |
| Env Var Update | An environment variable change triggered a hot-swap deployment |
Webhook triggers mean your Push to Deploy is working. API triggers show CLI or CI/CD pipeline deployments. Manual triggers indicate someone used the dashboard directly.
Triggering Deployments
You have options for deploying:
Deploy Now
Click "Deploy Now" for a quick re-deployment using your current configuration and the current branch. This is useful when you've made configuration changes (environment variables, container size, etc.) but your code hasn't changed. It's a quick way to apply settings without pushing new code.
Deploy with Custom Configuration
Click "Deploy with Custom Configuration" to override settings for just this deployment. Want to deploy from a different branch? Deploy to a different region? Set different environment variables for this specific deployment? This button lets you do all that without changing your saved settings.
This is handy for testing. Deploy from a feature branch to test before merging to main. Deploy to a different region to test regional deployment. Do all this without permanently changing your app's configuration.
Understanding Deployment Status
Each deployment has a status that tells you what happened:
- Success: Deployment completed successfully. Your app is now running this version.
- Failed: Something went wrong during build or startup. Your app is still running the previous version. Check the logs to see what failed.
- In Progress: Deployment is currently running. Galaxy is building your code and starting containers.
- Cancelled: You cancelled this deployment before it finished. Your app continues running the previous version.
Deployment Logs
Click any deployment to see what happened. You'll see logs in two stages:
Build logs show if your code is broken. Deploy logs show if your app can't start. Always check both when troubleshooting.
Deployment Timing
Each deployment shows timing information:
- Build time: How long it took Galaxy to build your code.
- Deploy time: How long it took to bring containers online and pass health checks.
- Total time: Complete end-to-end deployment time.
Watch these times over multiple deployments. If build time is increasing, your app might be getting more complex. If deploy time is increasing, health checks might be taking longer.
Automatic Deployments
When you push code to your deploy branch, Galaxy automatically detects the change and starts a deployment. This uses Push to Deploy, which is covered in deployment guides.
You'll see these automatic deployments in history with a webhook trigger. Each one was initiated by a Git webhook when code was pushed.
Manual Deployments
You can also trigger deployments manually from this page using "Deploy Now" or "Deploy with Custom Configuration". These show up with a manual trigger. Manual deployments are useful when you've changed configuration but not code, or when you need to redeploy a specific version.
Cancelled Deployments
Sometimes you might cancel a deployment that's in progress. Click "Cancel" while deployment is running, and Galaxy stops the process. Your app continues running the previous version unaffected.
Cancelling is instant. No impact on your live app.
Understanding Versions vs Deployments
This section shows deployments (every time code ran). But every deployment is tied to a Version (a code snapshot).
A single version can have multiple deployments. Deploy code once, you get one version and one deployment. Change a configuration variable and deploy again using the same code? Same version, new deployment (with an env_var_update trigger).
Want to understand this better? Head to Versions and Deployments for the full picture.
Need to understand versions vs deployments? They're related but different. Deployments are actions. Versions are code snapshots. One version can have many deployments.
Troubleshooting Failed Deployments
Build failed? Check build logs. Look for missing dependencies, syntax errors, or incorrect build commands. Usually the error message tells you exactly what's wrong.
Deploy failed? Check deploy logs. Look for errors about starting containers, binding ports, or health check failures.
App started but isn't responding? Logs might show your app is running but failing health checks. Check your app's code and health check endpoint configuration.
Still stuck? Reach out to support with your deployment ID. Include build and deploy logs so support can see exactly what happened.
What's Next?
Settings
The Settings section is your app's configuration hub. This is where you manage domains, Git settings, health checks, and other deployment options. Most changes here take effect on your next deployment.
Variables
Store sensitive configuration and secrets securely in Galaxy without committing them to Git.