jobtrackingapp/deploy/README.md

Deployment entry point

The deployment script and Gitea workflow live in this directory and .gitea/workflows/. The current deployment, health/readiness, rollback, and secret-handling guidance is in the repository infrastructure guide, especially deployment and disaster recovery.

Keep the server .env outside the repository. Do not run production deployment, restore, migration, or credential rotation as part of local documentation work.

MariaDB backup connection parsing uses scripts/parse-backup-connection.py (Python 3, already required by deployment preflight). Keys are case-insensitive and support the documented host/user/password/database aliases. Single/double-quoted values may contain semicolons and doubled quote characters. The dump contract requires one TCP host, a database and user, with port 1-65535 (default 3306); an empty password is retained. Duplicate aliases, control characters, host lists/socket paths and database path separators are rejected before dumping. This deliberately bounded parser is not the full MySqlConnector configuration engine. Additional connection options do not change existing dump-client TLS behavior; that qualification remains separate.

Run python scripts/test-deploy-backup.py for the offline synthetic dump-boundary regression. It extracts only the backup function and never executes the deployment entry point, contacts a database or reads the production environment.