Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,25 @@ See [STATUS.md](server/STATUS.md) to learn more about which features will remain
`.map`). `AppState::init` drops its own core-models bootstrap branch: its
"store did not exist" check ran after the store directory had been
created, and `Db::init_redb_file` already seeds a fresh store on open.

- `atomic_lib`: host-to-Drive mappings are reconcilable, so a control plane can
install hosted vanity subdomains without an agent that can sign on the
Drive's behalf. `Db::sync_drive_mappings` adds, repoints and removes a
desired set idempotently and scopes removal to the hosts it installed
itself (so `/bind-drive` bindings and the `localhost` entries from setup
survive); `Db::list_drive_mappings` and `Db::managed_alias_hosts` read the
table, which had no read path beyond a single-host lookup. Mapping keys are
now normalized, so a mixed-case `Host` header resolves the Drive it was
bound to instead of falling through to the store root.
- A host bound to a Drive now serves that Drive or answers 404. It used to
fall through to the store root when the bound Drive was missing — not synced
yet, or moved to another node — which on a multi-tenant server answers one
tenant's hostname with another namespace's content.
- New `--served-domain-suffix` / `ATOMIC_SERVED_DOMAIN_SUFFIX`: answer for
`*.<suffix>` so the request origin follows the hostname the visitor used,
without `--base-domain`'s other effect of also becoming the store's base
domain (which changes how subjects are normalized and migrated, and is not
something to switch on for a server that already holds data).
- The outbox drains over a live Iroh link too (`sync::peer::LivePeerCommitTransport`):
a device with no hub in reach delivers its queued writes to a paired peer as
signed `COMMIT` frames, which the peer validates and applies like a hub
Expand Down
32 changes: 32 additions & 0 deletions TESTING_COVERAGE.md
Original file line number Diff line number Diff line change
Expand Up @@ -845,6 +845,38 @@ Cloud Vault display metadata: `vaultAutoBackup.test.ts` verifies name/emoji enro
authenticated read from the real managed node. Plan purchase alone creates
no enrollment. Real Stripe-hosted test-card checkout remains a deployment check.

## Host-to-Drive routing and hosted vanity subdomains

`Tree::DriveMapping` is what makes one server answer for many hostnames. It
backs `/bind-drive` for self-hosters and hosted vanity subdomains for
`atomic-saas`, whose control plane reconciles it through
`Db::sync_drive_mappings`.

- `db::drive_mapping_tests`: the reconcile a managed node runs on every policy
poll — add, repoint, remove; idempotent on an unchanged list; scoped so a
binding it did not install (including the `localhost` / `127.0.0.1` entries
from `setup_test_env`, and anything bound by hand through `/bind-drive`) is
never removed; keys normalized so a mixed-case `Host` still resolves; empty
hosts and empty drives skipped.
- `db::resolver_tests::a_bound_host_whose_drive_is_missing_does_not_serve_the_store_root`:
the multi-tenant leak. A host bound to a Drive this node does not hold (not
synced yet, or migrated away) must 404 rather than fall through to the store
root, which would answer one tenant's hostname with another namespace's
content. This is the property that lets the control plane authorize a
certificate on reservation instead of only after a node confirms.
- `context::tests::a_served_domain_suffix_accepts_tenants_without_a_base_domain`:
`--served-domain-suffix` makes the request origin follow the hostname the
visitor used, without turning on `--base-domain` and with it the store's
subject normalization.
- Paired `atomic-saas` coverage (registry, plan gating, `/caddy-ask`, the
heartbeat report) is listed in that repo's
`planning/TEST_COVERAGE_AND_CI.md`.

**Not covered:** no test drives a real HTTP request against a vanity host
end to end — the reconcile and the resolver are tested separately, and joining
them needs the representative two-service environment. The multi-node gateway
routing that a second node would require does not exist yet.

## Error reporting and feedback

- `browser/data-browser/src/helpers/feedback.test.ts`: unavailable reporting, failed delivery, blank input and successful submission.
Expand Down
Loading
Loading