Configuration

Acme Platform provides a centralized configuration system that lets you manage environment variables, feature flags, and project settings across development, staging, and production environments.

Environment Variables

Set environment variables through the CLI or the dashboard. Variables are encrypted at rest and injected at build time or runtime depending on your deployment target.

Via CLI

# Set a single variable
acme config set DATABASE_URL "postgres://user:pass@host:5432/db" --env production

# Set multiple variables from a file
acme config import .env.production --env production

# List all variables for an environment
acme config list --env production

Via Dashboard

Navigate to Settings > Environment Variables in your project dashboard. Variables can be scoped to specific environments or shared across all of them.

Caution

Secrets like database passwords and API keys should never be committed to version control. Always use the config system or a dedicated secrets manager.

Configuration File

Create an acme.config.json in your project root for declarative configuration:

{
  "name": "my-project",
  "build": {
    "command": "npm run build",
    "output": "./dist"
  },
  "deploy": {
    "target": "cloudflare-workers",
    "routes": ["example.com/*"]
  }
}

Feature Flags

Feature flags let you toggle functionality without redeploying. Create flags in the dashboard and check them at runtime:

import { getFlag } from '@acme/sdk';

if (await getFlag('new-checkout-flow')) {
  // Render the new checkout experience
}

Flags support percentage-based rollouts, user targeting, and A/B testing out of the box.

Next Steps

Explore the Configuration Options reference for a complete list of all supported fields in acme.config.json.