Environments

Every Burrito site has two environments: production and test. Each environment runs its own container and has its own URL.

Production vs Test

Both environments are fully independent — they have separate containers, separate deployment histories, and can be rolled back individually.

Branch-to-Environment Mapping

Burrito maps git branches to environments automatically:

• main → production
• test → test

Pushing to any other branch has no effect. To deploy to test, create and push a test branch:

git push burrito main:test

Or maintain a separate test branch:

git checkout -b test
git push burrito test

Scale-to-Zero

To save resources, environments that receive no traffic are automatically stopped after a period of inactivity. When a request comes in:

1. The visitor sees a brief "waking up" loading page
2. The container starts in a few seconds
3. The page refreshes and serves your site normally

Subsequent requests are served immediately while the container is running. This happens transparently — you don't need to configure anything.

Environment URLs

Every environment gets automatic HTTPS with a certificate provisioned by Caddy:

• Production: https://yoursite.bntso.com
• Test: https://test.yoursite.bntso.com

No DNS configuration is needed on your end — Burrito handles DNS records and TLS certificates automatically.