Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(infra): describe how the page fills the restart stop list

Yudhi Armyndharisd7af9c590292
diff --git a/src/modules/infra/infra-config.controller.ts b/src/modules/infra/infra-config.controller.ts
index 017f4ac7a..55fd76813 100644
--- a/src/modules/infra/infra-config.controller.ts
+++ b/src/modules/infra/infra-config.controller.ts
@@ -479,9 +479,10 @@ export class InfraConfigController {
// (re)start. We deliberately do NOT infer teardown from the saved *_BUILTIN flag: the default
// data/.env.generated carries POSTGRES_BUILTIN=false, so a bare compose-profile restart would
// otherwise tear down the very backend the app is running on. The dashboard fills this list from the
- // live /infra/status builtIn flags at save time (running minus the new profiles). A container is
- // left running when that status read had failed, or when an environment pin keeps the app on it
- // (dropped above).
+ // live /infra/status at save time: the builtIn services minus the new profiles, plus a running container
+ // OpenWA created whose host the environment pins elsewhere, less any the saved config read back still
+ // reaches. A container is left running when that status read had failed, or when the next boot still
+ // dials it (dropped above).
// Only ever tear down OpenWA-managed services. An arbitrary profile name (or the empty string)
// would otherwise reach stopManagedService and, via container-name matching, could stop an unrelated
// container — so constrain teardown to the managed allowlist and drop anything else.