Personal Glance dashboard config.
0

Configure Feed

Select the types of activity you want to include in your feed.

CSS 89.0%
Go Template 7.3%
Dockerfile 2.1%
Shell 1.5%
38 1 0

Clone this repository

https://tangled.org/adam0.dev/home https://tangled.org/did:plc:u24sb7qxhqn7mb3aeld7mvvr
git@knot.zezura.xyz:adam0.dev/home git@knot.zezura.xyz:did:plc:u24sb7qxhqn7mb3aeld7mvvr

For self-hosted knots, clone URLs may differ based on your setup.



README.md

Glance Dashboard#

Personal Glance dashboard config.

Repo Size
Glance

Automatic updates#

The webhook service in webhook pulls this checkout when Tangled sends a signed push event for main. Glance watches its config and included files, so it reloads them without a container restart.

  1. Ensure /var/lib/glance is a Git checkout whose current branch tracks the desired Tangled remote and that UID 1000 can write to it.

  2. Add the contents of webhook/compose.yml to the Compose project containing Glance.

  3. Generate a secret with openssl rand -hex 32 and set the result as GLANCE_WEBHOOK_SECRET in the Compose environment.

  4. Build the updater on the host, then start it:

    podman build -t localhost/glance-updater:latest /var/lib/glance/webhook
    podman compose up -d updater
    
  5. In Tangled, open Settings > Hooks and create an active push webhook:

    • Payload URL: https://<your-glance-domain>/hooks/glance
    • Secret: the same value as GLANCE_WEBHOOK_SECRET

The Glance route can keep its Authentik middleware. The more-specific webhook route intentionally has no Authentik middleware because Tangled authenticates with its HMAC signature instead.

The updater fetches origin/main and resets the checkout to that commit. This overwrites tracked local changes and divergent local commits, but preserves untracked files. For a private repository, also mount read-only Git credentials into updater; a public HTTPS remote needs no credentials.