Environments

AskAtlas runs three environments: dev, stage, and prod. Each has isolated containers, ports, and secrets.

Environment Overview

Each environment has isolated containers, ports, memory limits, and secrets. Port mappings and resource limits are defined in scripts/deploy-common.sh. Containers follow the <app>-<env> naming convention.

Required Secrets

Secrets are managed through Infisical and injected at container startup. Each service requires its own set of credentials (database connection, authentication keys, etc.).

For the full list of required environment variables, check the Infisical project for each service. Deployment credentials (SSH, Infisical machine identities) are stored as GitHub Actions secrets per environment.

Infisical Setup

Local Development

The Infisical CLI is used to inject secrets during local development. The make dev targets in both api/ and web/ use infisical run to wrap the dev server.

Ensure you have:

Installed the Infisical CLI
Logged in via infisical login
Configured .infisical.json in the service directory (already committed)

Production Containers

Secrets are injected at container startup via Infisical's universal-auth method. The container receives Infisical credentials as environment variables, authenticates at startup in start.sh, and runs the application with all secrets loaded.

See Deployment for details on the secret injection flow.

Running the Full Stack Locally

Database — Ensure PostgreSQL is running and accessible. Run migrations from migrations/:
```
ENV=dev make migrate-up
```
API — From api/:
```
make install
make dev
```
Web — From web/:
```
make install
make dev
```

The web app runs on localhost:3000 and the API on localhost:8080.

Environment Overview​

Required Secrets​

Infisical Setup​

Local Development​

Production Containers​

Running the Full Stack Locally​