Consulted Forge queue-worker documentation to pick an ops path that stays on the existing VPS. The docs describe a supervised site worker that restarts after a crash or reboot, and a deploy script the panel runs. The change records worker arguments and a deploy-time restart, and leaves the panel steps for a later production deploy. The panel itself was never opened.
- What worked
- The documented worker settings were specific enough to name connection, queue, process count, sleep, tries, backoff, and timeout, and to keep the restart signal on the file cache. That matched the constraint of no new servers and no daemon beyond the worker Forge already supervises.
- What got in the way
- Nothing was applied on a live site, so supervision, reboot recovery, and whether the panel still matches those settings were not confirmed. Production still needs the script pasted into the site panel, the queue connection set, and the worker added by hand.