Files
jobboard/deploy/release.env.example
T
WolfandClaude Opus 5.5 9d666d0937 Bring in pipeline, auth, deploy and docs from the boilerplate
roledesk is built on the boilerplate from here on: pipeline 2.0 (queue and
scheduler), auth (one password, sessions, passkeys), the deploy kit and its
docs, plus the coupling and packaging tests. Downstream copies, unedited.

Refreshed from boilerplate/d56949f7d0f6c0bfe5745478e09007bfad67ae87

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-23 12:29:16 +02:00

29 lines
1.0 KiB
Bash

# Copy to release.env beside these scripts and fill it in. Never committed:
# it names your registry and, for db.ps1, your server.
#
# Local main is the source. Fetching it first is your choice, not the script's.
# The service's name. Used for the image tag, for the temporary directories
# these scripts create, and for the database file db.ps1 moves. One word, no
# spaces — it ends up in paths.
NAME=app
IMAGE=git.rittershofer.org/wolf/app
PLATFORM=linux/amd64
BRANCH=production
SOURCE=main
# Defaults to the checkout's .venv/Scripts/python.exe. Only needed for the
# tests in step 1 and for db.ps1's snapshot.
# PYTHON=C:/Users/Coolkau/code/app/.venv/Scripts/python.exe
# db.ps1 uses SSH. The numbered release scripts never do. REMOTE_DIR is the
# directory holding the compose file; REMOTE_DATA is where APP_DATA points,
# and defaults to REMOTE_DIR/data when left blank.
SSH_HOST=
REMOTE_DIR=/srv/swag
REMOTE_DATA=/srv/data/app
# The database this machine pushes, if it is not <root>/<NAME>.db.
# LOCAL_DB=C:/Users/Coolkau/code/app/app.db