Commit Graph
5 Commits
Author SHA1 Message Date
Sluijsens 25a3de0f1f Stops mixing gitea-workflow with the generic deploy-user placeholder
Same account, one name throughout instead of switching partway in.
2026-07-28 20:08:44 +02:00
Sluijsens 366e912e73 Renames the example deploy account to gitea-workflow
pi-deploy restated the obvious (it's on the Pi) without saying what
the account is actually for.
2026-07-28 19:51:10 +02:00
Sluijsens 960760c24e Makes the deploy account generic instead of per-project
No reason to mint a new system account for every project on the
same Pi - one shared, host-wide account works, namespaced by
directory per project underneath it.
2026-07-28 19:46:58 +02:00
Sluijsens 2f243f23c3 Fixes the account model deploy setup got wrong
webadmin turned out to be FTP-only and belongs to whoever uploads
customer websites, not to this pipeline. Switched to a separate
deploy account with its own home-directory paths, well away from
where the other sites live, and made the persistent website symlink
cross into webadmin's territory instead of the other way around.
2026-07-28 19:41:34 +02:00
Sluijsens cf80f827ae Deployment setup - the parts the workflow deliberately left out
Host setup checklist, real domains and ports, the database backup
script the deploy workflow only ever invokes, and a rollback plan.
Also drafted the FTPS switch procedure for whenever production moves
off the Pi, with a note that shared hosting is likely IIS-based -
that's a bigger change than swapping the transport.
2026-07-28 19:07:26 +02:00