Apps Menu

Notifications

Different notification events matter for different scenarios. Here's what you can get notified about:

Critical events (we recommend enabling these as a minimum):

• Deploy failed
• Build failed temporarily
• Build failed permanently
• App automatically stopped
• Certificate generation error

Resource issues (important if your app tends to consume lots of CPU or memory):

• Container unhealthy
• App unavailable

Setting Up Email Notifications

Email notifications are straightforward to enable:

1. Click the "Add New Notification" button
2. Select "Enable Email Notifications"
3. Choose which activity types you want to receive emails about
4. Click "Save"

If you have a personal account, you're done. If you're in an organization, you'll need to specify which team members should receive the emails. Go to the Members tab and toggle on each person who should get notified.

Setting Up Slack Notifications

Slack notifications let you route alerts directly into your team's communication flow.

First time setup:

1. Head to Slack's app directory and add an "Incoming WebHooks" app to your workspace (or visit Slack's help article)
2. Copy the webhook URL it generates (looks like https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX)

Configure in Galaxy:

1. Click the "Add New Notification" button
2. Select "Enable Slack Notifications"
3. Paste your webhook URL in the Slack Incoming WebHooks URL field
4. Choose which activity types trigger notifications
5. Optionally specify a custom Slack channel (or leave it empty to use the default channel you set up the webhook in)
6. Click "Save"

Pro tip: Set different webhook URLs for different channels if you want deploy failures going to #deployments but resource warnings going to #ops.

Per-App Notification Settings

Account-level notifications apply to all your apps, but sometimes you need fine-grained control. Galaxy lets you override account settings for individual apps.

To customize notifications for a specific app:

1. Click on the app name to open its management page
2. Go to the app's Settings
3. Find the Notifications section
4. Click "Enable Custom App Notifications"
5. Choose your activity types and enable or disable Email and Slack for just this app
6. Click "Save"

This gives you complete control. For example, you could silence notifications for a staging app while keeping them loud and clear for your production app. Each app's settings are independent, so you can mix and match exactly how you want.

Resources

See how many containers you're currently using versus your account limit. This is your quick snapshot of capacity. If you're approaching your limit or need more resources, use the "Contact Support" button to reach out to the Galaxy team about increasing your container allocation.

Integrations API

The Integrations API is your gateway to accessing Galaxy via GraphQL. If you want to automate deployments, manage apps programmatically, or integrate Galaxy into your development workflow, you'll need your API key from this section.

What you can do with the API:

• Automate app deployments
• Manage environment variables programmatically
• Query deployment history and app status
• Integrate Galaxy with your CI/CD pipeline
• Build custom tools and dashboards

Your API key is displayed in the Integrations API section. You can regenerate it if needed, and there are buttons to view or copy your key.

For detailed setup instructions and API documentation, check out the GraphQL API guide.

Authorized Domains

Why You Need This

If your Meteor app relies on Meteor as an identity provider, you need to whitelist the domains where your app handles authentication responses. Applications using Meteor authentication must specify authorized redirect URIs. These are your app's endpoints where Meteor sends authentication responses after a user logs in. Without them, Meteor won't allow the authentication flow to complete.

Adding an Authorized Domain

To add a new authorized domain:

1. Click the "Add New Domain" button
2. Enter your App Name (for your own reference, so you can identify it in the list later)
3. Enter your Redirect URI (the full URL where Meteor sends auth responses, like https://example.com/callback)
4. Click "Add New URI Field" if you need multiple redirect URIs for the same app
5. Click "Add Domain" to confirm

Multiple Redirect URIs

It's common to have different authentication endpoints for different environments. You can add as many redirect URIs as you need for a single app:

• https://localhost:3000/callback (local development)
• https://staging.example.com/callback (staging environment)
• https://example.com/callback (production)

Just click "Add New URI Field" to add another endpoint for the same app. This keeps everything organized under one app entry while supporting multiple environments.

Managing Your Domains

Each app can have multiple authorized domains. The App Name field is just for your reference, so use descriptive names that help you identify what each entry is for. You can edit or delete domains at any time if your authentication endpoints change.