
Deploy Glance | (Just Updated) Self-Hosted Dashboard, RSS Feeds and Server Stats, Login Password Generated
Glance self-hosted dashboard, RSS feeds and server stats behind a login
Just deployed
/app/config
Deploy and Host Glance on Railway
Built for an LLM agent to deploy and use. The deploy form has no fields to fill: the login password is generated, the whole dashboard sits behind that login, and the config lives on a volume. Glance is a self-hosted dashboard that puts RSS feeds, release trackers, Hacker News and Lobsters, server stats, bookmarks and a calendar on one fast page, a free alternative to a hosted start page.
About Hosting Glance
This template runs one service, glance: the upstream Glance v0.8.8 image, pinned by digest, through a thin wrapper, with a volume at /app/config that holds the dashboard config (glance.yml) and the session secret. One public domain serves the dashboard. The listener is on Railway's injected PORT, and the healthcheck is GET /api/healthz.
What the wrapper fixes. Upstream Glance has no login unless you write one into the config, so a plain deploy shows its dashboard to anyone who finds the domain. The wrapper writes a default config on first boot that puts every page behind a login: user admin, password from the ADMIN_PASSWORD variable. It keeps the session secret on the volume so logins survive a redeploy, trusts Railway's proxy headers, and refuses to start if ADMIN_PASSWORD is empty.
Using it. Open the domain and sign in as admin with ADMIN_PASSWORD. To change the dashboard, edit /app/config/glance.yml on the volume, or set a GLANCE_CONFIG variable holding a complete Glance YAML config: it replaces the file at every boot and can read ${PORT}, ${GLANCE_SECRET_KEY} and ${ADMIN_PASSWORD}. The default config is written once; changing ADMIN_PASSWORD later changes the login, because the config reads it at every start. Glance limits failed logins to 5 per 5 minutes per client address.
Agent contract
- Public URL:
https://RAILWAY_PUBLIC_DOMAIN(the generated domain of theglanceservice) - Private URL:
http://glance.railway.internal:8080 - Credentials: the variable
ADMIN_PASSWORDon theglanceservice is the password of the useradmin - Auth:
POST /api/authenticatewith a JSON body{"username":"admin","password":"ADMIN_PASSWORD value"}andContent-Type: application/jsonanswers 200 and sets thesession_tokencookie; send the cookie on every other call. Without it, pages redirect to the login (303) and/api/pages/PAGE/content/answers 401. Glance has no write API and no sign-up. - Health:
GET /api/healthzreturns 200
#!/bin/sh
# needs: RAILWAY_PUBLIC_DOMAIN, ADMIN_PASSWORD (variables of the glance service); also curl, grep, mktemp.
# write-auth: none - Glance has no write API; the only POST is the login, shown below with a wrong password
# signup: none - Glance has no account registration; the only user is `admin`, created from ADMIN_PASSWORD
R="https://$RAILWAY_PUBLIC_DOMAIN"; J="Content-Type: application/json"; C=$(mktemp)
n=0; until [ "$(curl -s -o /dev/null -w '%{http_code}' "$R/api/healthz")" = 200 ]; do n=$((n+1)); [ "$n" -le 60 ] || break; sleep 5; done
curl -s -o /dev/null -w "health: %{http_code}\n" "$R/api/healthz"
# a stranger is redirected to the login page and gets no widget data
curl -s -o /dev/null -w "page without login: %{http_code}\n" "$R/"
curl -s -o /dev/null -w "content without login: %{http_code}\n" "$R/api/pages/home/content/"
curl -s -X POST -H "$J" -d '{"username":"admin","password":"not-the-password"}' -o /dev/null -w "login wrong password: %{http_code}\n" "$R/api/authenticate"
# log in as admin with the generated password: the session cookie is set
curl -s -X POST -H "$J" -d "{\"username\":\"admin\",\"password\":\"$ADMIN_PASSWORD\"}" -c "$C" -o /dev/null -w "login: %{http_code}\n" "$R/api/authenticate"
curl -s -b "$C" -o /dev/null -w "page with login: %{http_code}\n" "$R/"
curl -s -b "$C" -o /dev/null -w "content with login: %{http_code}\n" "$R/api/pages/home/content/"
if curl -s -b "$C" "$R/api/pages/home/content/" | grep -q 'widget'; then echo "widgets rendered: found"; else echo "widgets rendered: MISSING"; fi
rm -f "$C"
Expected output against a fresh deploy (measured on a Railway deploy of the generated draft):
health: 200
page without login: 303
content without login: 401
login wrong password: 401
login: 200
page with login: 200
content with login: 200
widgets rendered: found
The refusals are the contract: page without login: 303, content without login: 401 and login wrong password: 401. Glance has no write endpoint and no account registration, so there is nothing else to open: the write-auth and signup lines in the snippet say so.
Why Deploy Glance on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Glance on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
- Agent-ready - no deployer fields, a contract block, and one script that proves the instance is healthy, a stranger sees nothing, and the generated password opens the dashboard.
- Private by default - every page sits behind a login instead of being open to the internet.
- Settings survive redeploys - the config and the session secret live on a volume.
- Pinned - the upstream image is pinned by digest and the wrapper by tag and digest.
Common Use Cases
- Personal start page - feeds, bookmarks, calendar and weather for one person on a private domain.
- Release and news tracker - GitHub releases, RSS, Hacker News and Lobsters in one view.
- Homelab and server overview - container and server stats next to the services you run.
- Team landing page - a shared page of links and feeds behind one login.
Dependencies for Glance Hosting
- The glance service with its volume, created by the template. A custom domain is optional; the wrapper does not need the domain name.
Deployment Dependencies
Template Content
