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

+4 -3
View File
@@ -1,13 +1,14 @@
# Run a published image, without cloning the source.
#
# 1. Put this file and a .env (copied from .env.example) in a folder.
# 2. The image below is the project's published one (tags: latest, or a
# commit such as :1412470). To build and publish your own instead:
# 2. The image below is the project's published one (tags: latest, a
# release such as :2026.11.6, or a commit such as :34879e7). To build and publish your own instead:
# docker build -t your-registry/simple-aircraft-manager-rails:latest \
# --build-arg APP_REVISION=$(git rev-parse --short HEAD) --build-arg APP_BUILT_AT=$(date -u +%FT%TZ) .
# docker push your-registry/simple-aircraft-manager-rails:latest
# 3. docker compose -f docker-compose.image.yml up -d
# 4. Open http://<server>:3000 and create the admin account.
# 4. Open http://<server>:3000 and create the admin account, with the setup
# code from: docker compose -f docker-compose.image.yml logs web | grep "Setup code"
#
# Updating: docker compose -f docker-compose.image.yml pull && docker compose -f docker-compose.image.yml up -d
# (database changes are applied when the container starts). Then: docker compose exec web bin/rails sam:doctor