chore: clarify Dockerloid workflow comments

This commit is contained in:
rmancinas committed 2026-10-13 18:04:43 -07:00
1 parent ac735a627e
commit 344319f456
1 file changed
+3 -3
+3 -3
View File
@@ -48,7 +48,7 @@
# # Database stack (full only) # # Database stack (full only)
# MYSQL_PASSWORD app-user password (matches DATABASE_URL) # MYSQL_PASSWORD app-user password (matches DATABASE_URL)
# MYSQL_ROOT_PASSWORD mysql root password # MYSQL_ROOT_PASSWORD mysql root password
# - the runner must reach Dockerloid (9443). It should also reach MySQL (3306) # - runner must reach Dockerloid API (7777) and MySQL (3306)
# for the migrate step, but that is no longer load-bearing: dispatch with # for the migrate step, but that is no longer load-bearing: dispatch with
# skip_migrate=true and the api container applies the migrations itself at # skip_migrate=true and the api container applies the migrations itself at
# start (docker/api-entrypoint.sh). `migrate deploy` is idempotent, so the # start (docker/api-entrypoint.sh). `migrate deploy` is idempotent, so the
@@ -202,8 +202,8 @@ jobs:
MYSQL_ROOT_PASSWORD: ${{ secrets.MYSQL_ROOT_PASSWORD }} MYSQL_ROOT_PASSWORD: ${{ secrets.MYSQL_ROOT_PASSWORD }}
BACKUP_TAG: ${{ github.event.inputs.tag }} BACKUP_TAG: ${{ github.event.inputs.tag }}
ALLOW_MISSING_CONTAINER: ${{ github.event.inputs.bootstrap }} ALLOW_MISSING_CONTAINER: ${{ github.event.inputs.bootstrap }}
# Dockerloid serves a self-signed certificate. Scoped to this step # Dockerloid uses HTTP on the LAN; this step does not need a TLS bypass.
# only, which does nothing but talk to Dockerloid. # Requests in this step go only to the Dockerloid API.
run: node deploy/scripts/pre-migrate-backup.mjs run: node deploy/scripts/pre-migrate-backup.mjs
# --- schema, forward-only --------------------------------------------- # --- schema, forward-only ---------------------------------------------