Files
rickyandClaude Opus 5.5 3ad6b9493a Compose files and .env.example catch up
- The compose files' steps say where the first-run setup code is (it's
  asked for since 2026.11.5), that new accounts come from the admin, and
  who adds aircraft; the published image's release tags are mentioned.
- docker-compose.yml passes APP_REVISION/APP_BUILT_AT to the build when
  set, so a locally built image shows its build on Admin → About.
- .env.example lists the optional push notification keys, APP_LOCALE and
  APP_IMAGE, which the README documented but it didn't.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 19:35:45 -05:00

34 lines
1.3 KiB
YAML

# Simplest self-hosting, built from this checkout: one container, SQLite and
# uploads in a named volume. To run a published image instead, see
# docker-compose.image.yml; behind Traefik (and Authentik), docker-compose.traefik.yml.
#
# cp .env.example .env # set SECRET_KEY_BASE (bin/rails secret), APP_HOST, FORCE_SSL
# APP_REVISION=$(git rev-parse --short HEAD) docker compose up -d --build # the build shows on Admin → About
# open http://localhost:3000 → create the admin account, with the setup code from:
# docker compose logs web | grep "Setup code"
#
# New accounts after that come from the admin (Admin → Users or Invitations).
# Only admins add aircraft unless Admin → Settings allows everyone.
services:
web:
build:
context: .
args:
APP_REVISION: ${APP_REVISION:-}
APP_BUILT_AT: ${APP_BUILT_AT:-}
restart: unless-stopped
ports:
- "3000:80"
env_file: .env
environment:
SOLID_QUEUE_IN_PUMA: "true" # background jobs run inside the web process
volumes:
- sam_storage:/rails/storage # databases + uploaded files: back this up
healthcheck:
test: ["CMD", "curl", "-fsS", "http://localhost/up"]
interval: 30s
timeout: 5s
retries: 3
volumes:
sam_storage: