Decide whether the domains system should live inside the console #254

New Issue

2026-10-24T05:12:33Z

cgalo5758 commented

2026-10-24 05:12:33 +00:00

The question

The domains system (the registry of custom domain names, members' claims on them, and the certificate check a TLS proxy asks before it issues a certificate for a wiki site) runs inside the console. Should it stay there, or become its own module or its own service?

What depends on the answer

Whether every wiki site keeps its certificate while the console is down or still starting. The proxy's check is answered by the console, so anything that keeps the console from serving keeps certificates from being issued. A deployment's sites lost their certificates after a reboot this way. #141 makes the console serve sooner; the coupling stays.
How the console treats its own dependencies. Part of why it must serve without Temporal is that this check lives inside it.
How integrations depend on the domains system (the wiki integration places names through it), and a second consumer of names, such as several wiki farms.

Options known so far

Keep it inside the console, with the certificate check depending on nothing but the database.
Separate it as its own module in the same process.
Run it as its own service that the console, the integrations and the proxy call.

None is preferred yet.

Decided when

The choice, its reasons and what would change it are written in docs/models/domains-registry.md, and an issue exists for any work it calls for.

## The question The domains system (the registry of custom domain names, members' claims on them, and the certificate check a TLS proxy asks before it issues a certificate for a wiki site) runs inside the console. Should it stay there, or become its own module or its own service? ## What depends on the answer - Whether every wiki site keeps its certificate while the console is down or still starting. The proxy's check is answered by the console, so anything that keeps the console from serving keeps certificates from being issued. A deployment's sites lost their certificates after a reboot this way. #141 makes the console serve sooner; the coupling stays. - How the console treats its own dependencies. Part of why it must serve without Temporal is that this check lives inside it. - How integrations depend on the domains system (the wiki integration places names through it), and a second consumer of names, such as several wiki farms. ## Options known so far - Keep it inside the console, with the certificate check depending on nothing but the database. - Separate it as its own module in the same process. - Run it as its own service that the console, the integrations and the proxy call. None is preferred yet. ## Decided when The choice, its reasons and what would change it are written in `docs/models/domains-registry.md`, and an issue exists for any work it calls for.

cgalo5758 added the

kind

design

area/domains area/ops labels 2026-10-24 05:12:33 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#254