zhangwenjian f5273f5a58 ci🔧: migrate before deploying, and roll back when the new version does not come up ...

Closes #871.

The deploy did docker rm -f then docker run. Nothing ran migrations, so
new code met old tables, and nothing checked the result - a container
that exits immediately left the site down with a green deploy.

Now, in order: pull the image, run the migration with it, and only then
touch what is running. A failed migration stops there, leaving old code
with the old schema, which is at least self-consistent.

The running container is renamed rather than removed, so it can be
started again unchanged if the new one does not become healthy. Healthy
means both an HTTP response and a database connection in the log: the
captcha endpoint answers without touching the database, so it alone
would call a container healthy that cannot reach MySQL.

2026-08-27 16:19:03 +08:00

..

ISSUE_TEMPLATE

Create config.yml

2022-08-18 13:02:42 +08:00

PULL_REQUEST_TEMPLATE

feat✨: pr_cn.md

2022-08-24 11:26:01 +08:00

workflows

ci🔧: migrate before deploying, and roll back when the new version does not come up

2026-08-27 16:19:03 +08:00

PULL_REQUEST_TEMPLATE.md

perf👌: Optimize go warnings

2023-08-01 22:38:41 +08:00