DOCSEARCHbyAlgolia
Submit Docs

Galaxy Cloud Documentation

website·Indexed 33 days ago

https://help.galaxycloud.app/

Documentation for deploying and managing applications on Galaxy Cloud. Includes guides for Meteor apps, web apps (Node.js, Python, AdonisJS), custom domain configuration, container memory management, and billing. Provides technical details on the Galaxy CLI, Monti APM, and dashboard settings for scaling, networking, and runtime logs.

Tokens
39.7K
Snippets
80
Records
330
Agent score
66%

What's inside Galaxy Cloud

  1. Overview of MongoDB Oplog Tailing for Meteor

    Oplog tailing allows Meteor applications to listen directly to MongoDB's operations log (a capped collection of write operations) instead of polling the database. This results in instant reactivity for observeChanges callbacks and reduced database load. Oplog tailing requires a MongoDB replica set; standalone instances are not supported.

  2. Manage apps using Dashboard Common Actions

    The top right of the app overview page provides quick action buttons based on the app's state and type:

    • Open App: Opens the live application in a new tab.
    • Settings: Access Git configuration, domains, and health checks.
    • Upgrade App: Navigate to the Plans section to change container size or plan tier.
    • Restart: Forces a clean restart without redeploying (useful for clearing transient issues).
    • Stop / Start: Pauses the app to avoid container charges or brings it back online.
    • APM (Meteor apps only): Opens Monti APM for performance monitoring (requires Professional plan).
    • SEO (Meteor apps only): Opens SEO configuration.

  3. Understand Galaxy Metal Infrastructure

    Galaxy Metal is the hosting platform's core infrastructure, built on bare metal servers with direct hardware access and no virtualization overhead. All Galaxy applications run on this infrastructure automatically. Key benefits include 3x faster builds, eliminated build queues, blue-green deployments for zero-downtime updates, and enterprise-grade security features like role-based access control and network policies.

  4. Understand Galaxy service availability and geographic restrictions

    Galaxy service availability is determined by international sanctions, trade restrictions, local laws, and regulatory compliance. Services are not available in restricted regions. Users are responsible for providing accurate geographic and payment information; misrepresenting location to bypass restrictions violates the terms of service and may lead to account termination.

  5. Understand Galaxy Cloud billing models

    Galaxy Cloud offers two primary payment structures:

    • Monthly Billing: Charged on the same date each month based on usage. No contract; cancel anytime.
    • Savings Plan (Annual): Pay upfront once per year for a 20% discount on total hosting costs. This requires a year-long commitment.

    Billing is based on resource consumption: larger containers and longer runtimes result in higher costs.

  6. Configure data residency for EU compliance

    Galaxy Metal uses a cloud-agnostic architecture. For users with strict data residency requirements, the EU region runs on OVHcloud (a French company headquartered in Roubaix). This ensures data stays within Europe on European-owned infrastructure, subject to EU jurisdiction rather than the US Cloud Act, at no additional cost.

  7. Understand Galaxy App Billing (Pay Per Minute)

    Galaxy apps (Meteor, Node.js, Python, or AdonisJS) are billed on a pay-per-minute basis, pro-rated to the second. Charges only accrue while the container is running. Costs are determined by the runtime, the plan (e.g., Free, Essentials, Professional, Sandbox, Production), and the container size (ranging from 256MB to 12GB). Stopping or deleting an app immediately halts these charges.

  8. Understand Galaxy Cloud app statuses

    The app overview dashboard displays the current state of your application. The following statuses indicate the app's lifecycle and health:

    • Pending Deployment: App created, no deployment yet
    • Queued: Job queued, waiting for worker
    • Building: Worker building Docker image
    • Deploying: Deploying to Kubernetes
    • Running: Successfully running
    • Unhealthy: Health checks failing
    • Crashed: Container crashed
    • Restarting: Attempting restart
    • Stopped: User stopped
    • Suspended: Admin suspended
    • Failed: Deployment failed
    • Deleted: Soft deleted

  9. Database management dashboard overview

    The main Databases menu provides a table view of all clusters showing name, type/version (MongoDB, PostgreSQL, Redis), cluster type (Standalone, Replica Set, Sharded), status, region, and creation date.

    Clicking a database name opens the management page with the following sidebar tabs:

    • Metrics: Performance data for CPU, memory, disk, and network.
    • Logs: Real-time activity stream.
    • Query Insights: Analysis of slow queries (where available).
    • Backups: History and manual snapshot creation.
    • Settings: Database-specific options.
    • Danger Zone: Database deletion.

  10. Configure MongoDB SSL for Node.js applications

    To secure a Node.js application connecting to Galaxy Database, download the SSL certificate from the MongoDB cluster's Overview page in the Galaxy dashboard. Place the certificate (e.g., galaxy-mongodb.crt) in a project directory (such as certs/). Use the tls and tlsCAFile options in the MongoDB driver to reference the certificate path. Ensure the MONGO_URL environment variable includes ssl=true and authSource=admin.
    // Using mongodb driver
const { MongoClient } = require('mongodb');
const path = require('path');

const certPath = path.resolve('certs/galaxy-mongodb.crt');

const client = new MongoClient(process.env.MONGO_URL, {
  tls: true,
  tlsCAFile: certPath,
  authSource: 'admin',
  connectTimeoutMS: 10000,
  serverSelectionTimeoutMS: 5000,
});

await client.connect();

// OR using mongoose
const mongoose = require('mongoose');
const path = require('path');

const certPath = path.resolve('certs/galaxy-mongodb.crt');

await mongoose.connect(process.env.MONGO_URL, {
  tls: true,
  tlsCAFile: certPath,
  authSource: 'admin',
  connectTimeoutMS: 10000,
  serverSelectionTimeoutMS: 5000,
});

  11. Galaxy platform architecture and isolation

    Galaxy's infrastructure is hosted on AWS and OVHCloud. The platform uses container-level isolation (via Docker and RKE2) to ensure separation of resources, processes, and environments. Each customer application runs in its own isolated container on dedicated virtual servers.

  12. Database features and capabilities on Galaxy

    All databases hosted on Galaxy include the following features:

    • Automatic Daily Backups: Data is protected daily without extra configuration. Manual backups can also be created in database settings.
    • Zero Data Transfer Fees: No charges for data moving between an app and its database on Galaxy.
    • Monitoring: Access to metrics for connections, memory, and CPU usage.
    • Security: Encryption in transit for all data moving between the app and database.
    • External Access: Databases can be connected to external clients (e.g., TablePlus, pgAdmin, MongoDB Compass) using the connection string from the dashboard.