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.
Domain Management
Your app gets a primary domain when you deploy. You also have options to add custom domains for professional branding.
Your App's Primary Domain
When you deploy, you choose your app's primary domain during the setup process. It's permanent and works immediately with HTTPS.
For Meteor apps, your domain looks like myapp.meteorapp.com. You pick the subdomain name, and if it's available, it's yours.
For Web Apps (Node.js, Python, AdonisJS), you also choose a custom subdomain during deployment. Something like myapp.sandbox.galaxycloud.app. Pick a name that's easy to remember and relevant to your app. If the subdomain is available, you can claim it.
Your primary domain never changes once set. You can't delete it, but you can toggle it on or off. It's permanent and always available to your app.
All domains get automatic HTTPS. Your app is always secure, no matter which domain you use.
One Custom Subdomain Per App
You can only have one custom Galaxy subdomain per app. Choose it wisely. If you need multiple URLs, consider using custom domains instead.
Custom Domain
Got your own domain? Connect it here for complete branding control. Use app.yourcompany.com or yourcompany.com directly.
Setting up a custom domain requires DNS configuration at your registrar (usually just pointing a CNAME record to Galaxy). Galaxy handles SSL certificates automatically, so your custom domain gets HTTPS automatically too.
Custom domains are only available on paid plans. Free plans are limited to your primary Galaxy-hosted subdomain.
For detailed instructions on DNS configuration, SSL certificates, and troubleshooting, see the Custom Domains guide.
Configuration
This section connects to your Git repository and configures deployment behavior.
Git Repository Settings
Manage which Git account connects to Galaxy and which repository you're deploying from. You can change these anytime.
Git Account: Which GitHub account Galaxy should use to access your repositories. If you want to switch accounts, you can disconnect and reconnect here.
Repository: Which repo contains your app code. Push to your deploy branch, Galaxy detects the change and automatically deploys.
Deploy Branch: Which branch Galaxy watches. Usually main or master, but you can use any branch. Every push to this branch triggers a deployment.
Change these settings if you need to deploy from a different repository, switch GitHub accounts, or watch a different branch.
Health Check Configuration
Galaxy monitors your app's health by checking a specific endpoint regularly. Set this to a route your app responds to quickly (like /health or /status).
If the health check fails repeatedly, Galaxy knows something's wrong. It might restart containers or alert you, depending on your plan.
Default Health Check Path
If you don't specify a health check path, Galaxy defaults to /. Make sure your app responds with a 200 status code at the root path, or configure a dedicated health check endpoint.
Don't have a health check endpoint? Your app's root path (/) works as a basic check. For more robust monitoring, consider adding a dedicated /health endpoint that verifies your app's critical dependencies (database connections, external services, etc.).
Build Commands (Web Apps)
For Node.js, Python, and AdonisJS apps, you can customize the build process:
Install Command: How Galaxy installs dependencies. Usually npm install or pip install -r requirements.txt.
Build Command: How Galaxy builds your app. For example, npm run build for TypeScript compilation or asset bundling.
Start Command: How Galaxy starts your app. Something like npm start or python app.py.
These commands run in order during deployment. Customize them if your app has non-standard requirements.
Meteor Settings Path (Meteor Apps)
For Meteor apps, you can optionally specify a path to a settings.json file in your repository. Galaxy reads this file during deployment and applies the settings automatically.
Leave this empty if you prefer to manage settings directly in the Galaxy dashboard through the Variables tab.
Only use the Settings File Path for non-sensitive configuration. Never commit secrets to your repository.
Danger Zone
At the bottom of Settings, you'll find destructive actions. These require confirmation and can't be undone.
Delete App: Permanently removes your app from Galaxy. All containers stop, all data is lost, and your domain becomes available for others to claim.
Think carefully before using these. There's no recovery option.
What's Next?
Plans
The Plans section is where you manage your app's resources. This is how you scale up when traffic increases, downsize when you want to save money, or adjust your hosting tier based on what your app actually needs.
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.