Skip to content

docs(routing): manual runbook for adding an additional *.samo.team host to a client - #186

Merged
samo-agent merged 1 commit into
mainfrom
docs/additional-host-runbook
Jul 20, 2026
Merged

docs(routing): manual runbook for adding an additional *.samo.team host to a client#186
samo-agent merged 1 commit into
mainfrom
docs/additional-host-runbook

Conversation

@samo-agent

Copy link
Copy Markdown
Collaborator

Summary

  • Adds a new section to docs/stack/routing.md documenting the manual procedure for giving a client app a second *.samo.team alias via a hand-authored control-plane Caddy vhost.
  • No samohost code change — deliberately a one-off manual fixture (rare operation, not worth a command).
  • Covers: host-sensitivity audit, VM Caddy host-lock probe, sites.d file shape (with header_up Host rewrite when needed), caddy validate + caddy reload (not systemctl reload), verification steps, rollback, caveats (canonical host, systemd NAMESPACE quirk), and the field-record.samo.team worked example.

What is NOT changed

  • No code, no migrations, no Playwright scenarios (docs-only MR).
  • AppRecord.mainHost remains a single scalar — this runbook explicitly documents the workaround, not a platform feature.

Placement

Appended to docs/stack/routing.md (the existing home for control-plane-as-router + domain map + CF tokens) before the existing vhost-template-caveat section. No new files; no links needed to update.

…st to a client

Documents the hand-authored control-plane Caddy vhost pattern used to give
a client app a second *.samo.team alias when AppRecord.mainHost is
host-locked. Covers host-sensitivity audit, VM Caddy probe, sites.d file
shape, validate/reload steps, caveats (canonical host, systemd quirk), and
the field-record.samo.team worked example.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@samo-agent
samo-agent merged commit e79f9a8 into main Jul 20, 2026
1 check passed
@samo-agent
samo-agent deleted the docs/additional-host-runbook branch July 20, 2026 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant