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>
This commit is contained in:
rickyandClaude Opus 5.5 committed 2026-11-15 19:35:45 -05:00
1 parent 9adbc3d0a8
commit 3ad6b9493a
4 files changed
+25 -6

No files matched your search

+2
View File
@@ -4,6 +4,8 @@
# the names to your Traefik setup. In .env: APP_HOST=aircraft.example.com, FORCE_SSL=true.
#
# docker compose -f docker-compose.traefik.yml up -d
# Then open https://aircraft.example.com and create the admin account with the
# setup code from: docker compose -f docker-compose.traefik.yml logs web | grep "Setup code"
#
# Authentik: create the proxy provider and the unauthenticated URL list as in
# docs/authentik.md, then uncomment the middleware lines below. Leave them out