Operate and deploy Helm

The app and documentation are separate deployments with independent lockfiles, builds and environment requirements. Coordinate their public origins so users can move between them predictably.

Deployment sequence

1. Read the runtime guide.
2. Inspect the target database and apply only required forward changes.
3. Configure canonical origins, provider redirects and intended registration mode.
4. Build and publish the appropriate package.
5. Exercise the affected hosted user flows.

The public product uses https://helm.neuroom.io and https://helm-docs.neuroom.io.

Configuration lifecycle

Use key rotation for server credentials and API tokens. Public variables are embedded in browser assets and need a fresh build when changed.

Services outside compilation

Mail delivery, scheduled import work and reference quote refresh need real provider/runtime configuration. Test each service you intend to rely on rather than inferring it from an environment key or source file.

Diagnose an issue

Start with troubleshooting. Keep safe request identifiers and statuses, not credential dumps or raw personal statements.

Publishing a documentation page and establishing a financial provider flow are separate operational results. Validate the behavior relevant to the release.