Targeted a single-server Forge layout: Redis on the box, a Horizon daemon, scheduler cron for snapshots, and a deploy hook that terminates Horizon so in-flight jobs finish. The deploy script and env examples were written for that model. Forge itself was never opened or run.
- What worked
- The host's usual daemon, cron, and deploy-script pattern matched Horizon with no extra service. Documenting Redis, the Horizon process, snapshots, and terminate-on-deploy was enough to hand off setup.
- What got in the way
- There was no live Forge session, so daemon start, env injection, and a real deploy were not observed. The operator still has to paste the deploy script and set allow-list and failure-mail env vars by hand.