Deployments Guide

Learn how Aureon builds, releases, and manages your application deployments.

1. How Deployments Work

A deployment represents an immutable snapshot of your code running on Aureon infrastructure. When a deployment is initiated:

  1. Source Ingestion: Aureon pulls the specific Git commit SHA.
  2. Framework Detection: The build engine inspects configuration files to select the appropriate builder.
  3. Dependency Resolution: Dependencies are installed using your package manager lockfile (package-lock.json, yarn.lock, or pnpm-lock.yaml).
  4. Compilation: Your build command compiles TypeScript, bundles assets, and optimizes code.
  5. Release & Health Checks: The built artifact is packaged into a container or edge bundle and validated against platform health checks.
  6. Traffic Routing: Edge routers update traffic routing with zero downtime.

2. Deploying from Git

Git-based deployment is the standard way to ship on Aureon. Whenever you push code to GitHub:

git add .
git commit -m "Update application"
git push origin main

Aureon receives a webhook event, creates a new deployment, and begins the build pipeline automatically.

3. Preview Deployments vs. Production Deployments

  • Production Deployments: Triggered by pushes to your primary branch (e.g. main). They serve traffic on your primary production domain and live application URLs.
  • Preview Deployments: Triggered by pushes to feature branches or pull requests. Each preview receives a unique, immutable URL (e.g. project-git-feature-aureon.app) allowing you to test changes before merging.

4. Deployment History & Audit Logs

The Deployments tab displays every past release, including:

  • Commit message and author.
  • Git branch and commit hash.
  • Deployment duration and build timestamp.
  • Deployment status (Ready, Failed, Building, Cancelled).

5. Rolling Back a Deployment

If a recent release introduces an unexpected bug, you can instantly roll back to any previous stable deployment:

  1. Open your project and go to the Deployments tab.
  2. Locate the last known working deployment.
  3. Click the options menu (...) and select Promote to Production.
  4. Aureon re-routes production traffic to that build immediately without requiring a rebuild.

6. Deployment Status Indicators

Deployments move through clear status states:

  • Queued: The deployment is registered and waiting for an available build worker.
  • Building: Source code is being downloaded, dependencies installed, and assets compiled.
  • Deploying: Containers are provisioning, starting up, and undergoing health checks.
  • Ready: The application passed all checks and is actively serving traffic.
  • Failed: An error occurred during dependency installation, compilation, or container startup.
  • Cancelled: The deployment was aborted by a user before completion.

Explore

Pages
Buy