Skip to content

Glance — Runbook

Config changes not showing

Glance reads glance.yml at startup. After a config deploy, the container must be recreated for changes to take effect. The infra-apps playbook uses recreate: always to handle this automatically.

If changes still don't appear after a deploy:

  1. Hard refresh the browser — Ctrl+Shift+R (or Cmd+Shift+R on Mac). Glance serves static assets that may be browser-cached.
  2. Restart the container manually: 
    ssh [email protected] "pct exec 119 -- docker restart glance"
  3. Verify the config was deployed: 
    ssh [email protected] "pct exec 119 -- grep '<search term>' /opt/glance/glance.yml"

Cached API responses

custom-api widgets cache responses per their cache: setting (e.g., cache: 2d). After changing an upstream API or n8n workflow that feeds a widget, Glance continues serving stale data until:

  • The cache expires naturally, OR
  • The container is restarted: 
    ssh [email protected] "pct exec 119 -- docker restart glance"

View logs

ssh [email protected] "pct exec 119 -- docker logs glance --tail 50"

Redeploy

Push changes to services/glance/ or trigger the infra-apps workflow manually. The workflow deploys all of: Gatus, Ntfy, Glance, and external OAuth2 proxies.