Hosting model for client/demo sites: shared vs. dedicated nodes #1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Decide and build a hosting model for client/demo sites: shared multi-tenant host vs. a dedicated node per client.
Today's demo model is path-prefixed sessions on one shared
webhost (per-session content repos, TTL expiry viacreate-session.sh/destroy-session.sh). This issue is about adding the option of a client getting its own dedicated node instead of (or alongside) that shared model.Depends on / entangled with the
site-separationbranch (sitemeta/sitectl, extracting a site into its own repo) — that work is what makes a site portable enough to actually place on a different node, so it's a likely prerequisite rather than parallel work.Open questions:
site-separationmerging, or can a first cut start against today's engine?Reconciled against
docs/separation-plan.md(branchsite-separation), section "Host layout":So this issue's engine-side half (not hard-coding one-site-per-host — install dir, webroot, API port, systemd unit name, nginx server block all per-site-configured) is covered by #7 (Release A step 4 — the per-site release-directory/blue-green layout already generalizes this, following the existing
coach-api-demo@<token>pattern). The actual shared-vs-dedicated-node decision, and Terraform/multi-site-Ansible provisioning, is explicitly out of scope for this repo and belongs in the infra repo instead — this issue should track that decision and any coaching-site-repo-side follow-up only, not duplicate #7's engine work.