A deployment's own settings can only be changed by redeploying it #55

New Issue

2026-09-21T07:18:17Z

cgalo5758 commented

2026-09-21 07:18:17 +00:00

What a person cannot do today

See or change what a deployment is configured with. Around forty keys are set through flags, environment and files and described in docs/environment-reference.md; the only ones editable from the console are the integration keys, on each integration's settings page, and those apply at the next start. The deployment's own name, its support address, the base address used in links and the domains policy knobs have no surface at all.

What they should be able to do

Open one page that lists every configuration the deployment has: the values that come from the environment and the infrastructure ones shown read-only with the source each came from, the rest editable, with the ones that only take effect at the next start saying so. The setup checklist is reachable from it while it is unfinished.

Why it matters

A deployment operator who wants to change the support address should not need shell access, and one page that shows every value with its source is the only way to know what a running deployment is actually using.

Where

The configuration layer that already declares keys with their defaults and help text and layers operator-set rows over the environment at boot, recording a source per key; the settings table that holds runtime values, which carries one key today; the integration settings page, which is the surface to generalize.

Done when

An inventory exists first, because a settings page with two rows is a menu: the operator-facing keys separated from the infrastructure ones. Then the page lists both groups, edits what is editable, states each value's source and its restart behaviour, and the values read on every request take effect without a restart. Two backing stores behind one page is an implementation detail, not two pages. The Domains page's policy section becomes a link into this page's section instead of restating the values.

Migrated from status/issues.md at b7a0e15

## What a person cannot do today See or change what a deployment is configured with. Around forty keys are set through flags, environment and files and described in [`docs/environment-reference.md`](https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/b7a0e15/docs/environment-reference.md); the only ones editable from the console are the integration keys, on each integration's settings page, and those apply at the next start. The deployment's own name, its support address, the base address used in links and the domains policy knobs have no surface at all. ## What they should be able to do Open one page that lists every configuration the deployment has: the values that come from the environment and the infrastructure ones shown read-only with the source each came from, the rest editable, with the ones that only take effect at the next start saying so. The setup checklist is reachable from it while it is unfinished. ## Why it matters A deployment operator who wants to change the support address should not need shell access, and one page that shows every value with its source is the only way to know what a running deployment is actually using. ## Where The configuration layer that already declares keys with their defaults and help text and layers operator-set rows over the environment at boot, recording a source per key; the settings table that holds runtime values, which carries one key today; the integration settings page, which is the surface to generalize. ## Done when An inventory exists first, because a settings page with two rows is a menu: the operator-facing keys separated from the infrastructure ones. Then the page lists both groups, edits what is editable, states each value's source and its restart behaviour, and the values read on every request take effect without a restart. Two backing stores behind one page is an implementation detail, not two pages. The Domains page's policy section becomes a link into this page's section instead of restating the values. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

enhancement

area/operator-ui area/ops labels 2026-09-21 07:18:17 +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#55