Projects & Workload Management

Learn how Aureon organizes applications and deployments into projects.

1. Projects Explained

In Aureon, a Project is the top-level container for an application workload. A project encapsulates:

  • The linked Git repository and target branch.
  • Framework and build settings (build commands, root directories, output directories).
  • Environment variables and secrets scoped to production or preview environments.
  • Custom domains and SSL certificates.
  • Complete deployment history and live container workloads.

2. Creating a Project

The standard project creation workflow is straightforward:

  1. Create Project: Click "New Project" in the console.
  2. Connect Repository: Select an authorized GitHub repository.
  3. Select Branch: Choose the primary branch that represents production.
  4. Review Configuration: Confirm build scripts, package manager, and output paths.
  5. Configure Variables: Add any required build or runtime environment keys.
  6. Deploy: Aureon builds and releases the application immediately.

3. Project Settings

Project settings allow you to fine-tune how Aureon builds and runs your workload:

  • General Settings: Project name, linked Git repository, and root directory (useful for monorepos).
  • Build & Output Settings: Custom build command (e.g. npm run build), output directory (e.g. dist, build, or .next), and install command.
  • Environment Variables: Encrypted key-value pairs categorized by environment.
  • Domain Management: Assign custom apex domains and subdomains.
  • Branch Settings: Configure which branches trigger automatic production releases versus preview releases.

4. Project Deployments

Every commit or manual redeployment creates an immutable deployment record associated with your project. You can inspect previous versions, review past logs, download artifacts, and initiate instant rollbacks at any time.

5. Project Environments

Aureon projects support environment isolation:

  • Production Environment: The live workload attached to your custom domains and primary Git branch.
  • Preview Environment: Ephemeral, branch-specific deployments created on pull requests for pre-release testing.

6. Deleting a Project

Deleting a project is a permanent, destructive action. When a project is deleted:

  • All associated deployments and build histories are deleted.
  • Active runtime containers are immediately stopped and decommissioned.
  • Custom domains bound to the project are released.
  • Environment variables and secrets are permanently erased.
Warning: Always ensure you have backups of any persistent database data and have updated DNS records before deleting a project.

Explore

Pages
Buy