# Copy to release.env. One file, read by both halves of the release: the bash # scripts (_common.sh), which run in the WSL distro that holds the checkout, and # the PowerShell ones (_common.ps1, wsl-setup.ps1), which run on Windows. Both # read KEY=VALUE lines and neither runs the file as shell, so $HOME and ~ are # not expanded. Local main is the source; fetching is your choice. Never # committed: it names your registry and, for db.sh, your server. # # Where the checkout is: the distro's name and the path inside it, as # docs/Install WSL.md lays them out, with the checkout folder's name last. # wsl-setup.ps1 writes them into the profile commands, and steps 2 and 3 find # step 1's export at \\wsl.localhost\\\release\. DISTRO=claudebox CHECKOUT=/home/claude/cboxcode/jobboard # The compose service, SERVICE in deploy/server/*.sh. Used by db.sh, on the # Linux side, for the snapshot names (-.db.gz, as backup.sh writes # them) and the start command it prints. One word, no spaces. NAME=app # Windows side, used by steps 2 and 3. wslc builds for the machine's own # architecture (linux/amd64 here) and has no --platform. IMAGE=git.rittershofer.org/wolf/app # Linux side, used by step 1: which branch is tested, and which one it promotes. BRANCH=production SOURCE=main # Linux side, used by step 1 and by db.sh's snapshot, in the distro. Defaults to # the checkout's .venv/bin/python (a WSL path, /home//...). # PYTHON=/home//cboxcode/jobboard/.venv/bin/python # db.sh 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 the one the app's config names # (`database` in config.yaml, roledesk.db in the checkout without one). # LOCAL_DB=/home//cboxcode/jobboard/roledesk.db