The config panel currently shows the admin container's own environment, which is misleading — during the 2026-07-10 env-drift debugging it reported the loop's flags as NOT SET while they were set. It should inspect each service's env through the mounted docker socket (GET /containers//json .Config.Env) and display per-service effective config.
The config panel currently shows the admin container's own environment, which is misleading — during the 2026-07-10 env-drift debugging it reported the loop's flags as NOT SET while they were set. It should inspect each service's env through the mounted docker socket (GET /containers/<id>/json .Config.Env) and display per-service effective config.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The config panel currently shows the admin container's own environment, which is misleading — during the 2026-07-10 env-drift debugging it reported the loop's flags as NOT SET while they were set. It should inspect each service's env through the mounted docker socket (GET /containers//json .Config.Env) and display per-service effective config.