mARTin-B78
6f4fe219dc
Some checks are pending
Playwright Tests / test (push) Waiting to run
There were two near-identical update scripts and they drifted: the npm ci fix from 1.114.1 only ever landed in update-app.sh, so the boot path kept running npm install. my-weekly-todo-update.service now runs update-app.sh, and boot-update.sh is a shim kept only so a not-yet-recopied unit still works. To be usable at boot the script needed three things it did not have: - Skip the rebuild when HEAD already matches origin/main and a standalone build exists, so a reboot is not a full rebuild every time (--force overrides). - Do not restart PM2 when its daemon is not up yet. At boot this unit runs before pm2-root.service, and probing with `pm2 describe` would spawn a stray daemon that races the real service, so it checks the pid file. - A flock single-instance lock, so a boot run and a manual run cannot install into the same tree at once. It also picks up prisma migrate deploy / generate and the .env copy that only the boot script had. The log moved to /var/log/my-weekly-todo-update.log. v1.115.2 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| backup-db.sh | ||
| boot-update.sh | ||
| create-test-user.ts | ||
| deploy.sh | ||
| docker-entrypoint.sh | ||
| generate-vapid-keys.ts | ||
| lxc-setup.sh | ||
| my-weekly-todo-update.service | ||
| push-scheduler.ts | ||
| seed-connection.ts | ||
| supabase-setup.sh | ||
| test-cloudkit-reminders.py | ||
| update-app.sh | ||
| update-server.sh | ||
| verify-schema.ts | ||