To self-host Glance on a managed VPS is to gather your news feeds, the weather and the status of your services on a single page of your own, on a server that our teams keep up to date and monitor day and night. Glance is a free, open source dashboard under the AGPL-3.0 license, a single Go program configured in YAML. This guide follows its official Docker image at version 0.8.8, and we ran every command on a Simafri VPS before writing it: installation with Docker Compose, a first page of widgets, HTTPS, login, configuration reload, backups and updates.
By Simon Vasconcelos Lee
Published on 21 November 202611 minute read
glanceapp/glance, a config folder mounted in the container, and port 8080 published on 127.0.0.1 behind an HTTPS reverse proxy..env file. Set proxied: true behind the proxy, so that its brute-force protection sees each visitor’s address.glance.yml as soon as you save it, and keeps the previous version running if the new one has an error. config:validate checks a file before you save it.Glance is a self-hosted dashboard that puts your feeds in one place. Each page holds up to three columns, and each column a stack of widgets, all described in a YAML file. Glance fetches their data when you open the page and keeps it in memory for a while, so nothing runs in the background between two visits.
It ships as one binary of about 16 MB, for Linux, Windows and macOS, and as a Docker image for x86-64, ARM64 and ARMv7. Pages adapt to phones, and themes and custom CSS change its look.
Glance is published under the GNU Affero General Public License, version 3 (AGPL-3.0). You can use it free of charge, for yourself, your family, your club or your company, copy it and modify it. If you modify it and let other people use your version over the network, you offer them its source code under the same license. The software is provided without warranty.
Glance is one of the lightest applications you can self-host. Here is what we measured on our test VPS, with the page of this guide loaded in a browser:
Glance therefore fits easily beside other applications. On a managed VPS, tell us what you plan to run on the server and we will recommend the right size.
The official image, glanceapp/glance, contains the Glance binary on Alpine Linux and reads its configuration from /app/config/glance.yml. On a server with Docker Engine and its Compose plugin, installed from Docker’s repository for Ubuntu, create a folder such as /opt/glance with a config folder inside, then put this compose.yaml in it, based on the manual Docker Compose installation of the README:
mkdir -p /opt/glance/config && cd /opt/glance
services:
glance:
image: glanceapp/glance:v0.8.8
restart: unless-stopped
env_file: .env
volumes:
- ./config:/app/config
ports:
- "127.0.0.1:8080:8080"
127.0.0.1: the README publishes it on every address of the server. Published locally, Glance is reachable only through the reverse proxy.config folder, mounted whole: Glance watches its file for changes, and on our test VPS it reloaded on every save, including when the file was replaced, as sed -i does.env_file: .env passes the secret key and the password hash to the container, where the configuration reads them.latest. A full version, here v0.8.8, lets you choose when each update happens.Then the configuration, in config/glance.yml. It sets Glance for the reverse proxy, turns on its login, and describes a first page with four widgets, which the next sections explain:
server:
proxied: true
auth:
secret-key: ${GLANCE_SECRET_KEY}
users:
admin:
password-hash: ${GLANCE_ADMIN_PASSWORD_HASH}
pages:
- name: Home
columns:
- size: small
widgets:
- type: weather
location: Paris, France
units: metric
hour-format: 24h
- type: calendar
first-day-of-week: monday
- size: full
widgets:
- type: rss
title: News
limit: 10
collapse-after: 5
cache: 2h
feeds:
- url: https://selfh.st/rss/
title: selfh.st
- url: https://github.com/glanceapp/glance/releases.atom
title: Glance releases
- size: small
widgets:
- type: monitor
title: Services
cache: 1m
sites:
- title: Website
url: https://www.example.com
- title: Glance
url: https://glance.example.com
check-url: http://localhost:8080/api/healthz
The two secrets go in a .env file. The image generates both: secret:make a random key that signs the sessions, and password:hash the bcrypt hash of a password, here a random one. Create the file readable by root only:
umask 077
GLANCE_PASSWORD=$(openssl rand -hex 12)
printf "GLANCE_SECRET_KEY=%s\nGLANCE_ADMIN_PASSWORD_HASH='%s'\n" "$(docker run --rm glanceapp/glance:v0.8.8 secret:make)" "$(docker run --rm glanceapp/glance:v0.8.8 password:hash "$GLANCE_PASSWORD")" > .env
umask 022
echo "Glance password for admin: $GLANCE_PASSWORD"
Note the password shown on the last line: only its hash is stored. The single quotes around the hash keep Docker Compose from reading its $ signs as variables. Check the configuration with the image, then start Glance:
docker compose run --rm glance config:validate
docker compose up -d
docker compose logs glance
curl -s http://127.0.0.1:8080/api/healthz
A valid configuration passes config:validate without a word. The log ends with “Starting server on :8080”, and the health check answers with an empty body and the status 200. Glance was ready within seconds on our test VPS.
The container serves Glance over HTTP, on port 8080 of the server. HTTPS is handled by a reverse proxy in front of it, which must forward the visitor’s address in X-Forwarded-For. We tested Caddy, installed from its official Debian and Ubuntu repository: it obtains the Let’s Encrypt certificate itself, renews it, and sets this header by default.
glance.example.com {
reverse_proxy 127.0.0.1:8080
}
sudo systemctl reload caddy
proxied: true, in the server block of the configuration, tells Glance to read the visitor’s address from X-Forwarded-For. The next section shows why it matters.Since version 0.8, Glance has its own login, turned on by the auth block of the configuration. Without it, anyone who knows the address reads your dashboard. Open your address: Glance shows its login page. Sign in with admin and the password shown when you created .env.
session_token cookie, marked Secure, HttpOnly and SameSite=Lax, valid for 14 days. The icon at the top right of each page signs you out.proxied: true: without it, Glance sees every request coming from Docker’s network, as if all visitors shared one address. We tried it: five wrong passwords then locked everyone out, the right password included. With it, the block applies only to the address that failed.users, each with its own password-hash, generated the same way.Generate a new hash, replace its line in .env, then recreate the container, since Glance reads environment variables only when it starts:
umask 077
GLANCE_PASSWORD=$(openssl rand -hex 12)
sed -i "/^GLANCE_ADMIN_PASSWORD_HASH=/d" .env
printf "GLANCE_ADMIN_PASSWORD_HASH='%s'\n" "$(docker run --rm glanceapp/glance:v0.8.8 password:hash "$GLANCE_PASSWORD")" >> .env
umask 022
docker compose up -d
echo "New Glance password for admin: $GLANCE_PASSWORD"
On our test VPS, the old password was refused at once, but the session opened with it stayed valid: sessions are signed with the secret key, not with the password. To sign every browser out, give Glance a new secret key as well:
umask 077
sed -i "s|^GLANCE_SECRET_KEY=.*|GLANCE_SECRET_KEY=$(docker run --rm glanceapp/glance:v0.8.8 secret:make)|" .env
umask 022
docker compose up -d
The session opened before was then sent back to the login page. Keep the same key otherwise: on our test VPS, sessions survived a restart of the container because the key did not change.
The first page of the configuration is the home page, and every page appears in the navigation bar, in order. A page holds one or two full columns, which share the width, and up to three columns in all; a small column is 300 pixels wide. Here is what the four widgets of our page do, all checked in a browser on our test VPS:
weather shows the forecast of the day in two-hour bars, from Open-Meteo, for the first place its geocoding finds under location. A place it cannot find stops Glance from starting, so keep the form “city, country”.calendar shows the month, here starting on Monday.rss mixes several feeds, newest first. Our page showed the latest issues of selfh.st and, from the Atom feed of the releases of Glance, version 0.8.8. cache: 2h fetches the feeds at most every two hours.monitor sends a request to each site and marks it OK when it answers 200, with the response time. check-url checks another address than the one the title links to: inside the container, localhost:8080 is Glance itself, and /api/healthz its health check. Statuses other than 200 can be accepted with alt-status-codes.Every widget accepts a title and a cache duration, such as 30s, 5m or 2h. The configuration documentation describes each widget and its options, and the README of the project links to preconfigured pages and community widgets.
The docker-containers widget, which lists your containers, needs the Docker socket mounted in Glance. That socket gives full control of Docker, and so of the server: we left it out of this guide. If you add it, a proxy that exposes the socket for reading only, such as docker-socket-proxy, which the documentation mentions, limits what Glance can do.
Glance reloads glance.yml as soon as it changes: save the file, then refresh the page. On our test VPS, each save printed “Config file changed, reloading...” in the log, whether the file was rewritten in place or replaced by sed -i. The reload clears the cache, so every widget fetches its data again.
A mistake does not take the dashboard down. We saved a widget type with a typo: the log printed “Config has errors: line 19: unknown widget type: calendr”, and Glance kept serving the previous configuration until the file was fixed. To check a file before you save it, or after you edit it:
docker compose run --rm glance config:validate
docker compose logs --since 5m glance
The first command prints the error and its line, here “Config file is invalid: line 19: unknown widget type: calendr”, and nothing when the file is valid. Check before any restart too: Glance refuses to start with an invalid configuration. Changes to .env, unlike the configuration, need docker compose up -d.
Glance keeps no data of its own: everything lives in /opt/glance, in three files, compose.yaml, .env and config/glance.yml, plus any file you add to config. Our archive weighed less than 1 KB. Since .env holds the secret key, create it readable by root only:
umask 077
tar -czf glance-$(date +%F).tar.gz -C /opt glance/compose.yaml glance/.env glance/config
umask 022
Schedule this copy and send it off the server. Stored on the disk, the folder is also included in the server’s nightly backups. The to-do list widget keeps its tasks in each browser, not on the server.
On the same server, or on a new one with Docker installed, extract the archive into /opt and start Glance:
tar -xzf glance-2026-11-20.tar.gz -C /opt
cd /opt/glance && docker compose up -d
We tested it on our VPS: Glance stopped, its folder deleted, then the archive extracted. Glance answered again a few seconds later, and the administrator signed in with the same password.
Glance published four releases between May and November 2026, the last one with security fixes, and the image follows on Docker Hub with the same tag. This guide pins v0.8.8, the latest release when we tested it: check the releases page for a newer one, and read its notes, which list the changes that need a new configuration. Then change the tag in compose.yaml, pull the new image, check your configuration with it and recreate the container:
docker compose pull
docker compose run --rm glance config:validate
docker compose up -d
docker image rm glanceapp/glance:v0.8.7
config folder.Self-hosting means running the server on top of the application. On a managed VPS, our teams take charge of the server and proactively monitor your instance; Glance remains your dashboard, with your pages and your settings.
| Topic | Our teams | You |
|---|---|---|
| The server | System and security updates, server interventions included | The timing that suits you |
| Monitoring | Server monitored 24/7, with intervention without waiting for your call | Your pages, widgets and feeds in Glance |
| Glance | Proactive monitoring: errors, slowdowns and disk space spotted, fix recommended | Its installation, updates and configuration, which you apply, yourself or through your AI assistant |
| Access | The server and its HTTPS front, monitored | Accounts, passwords and the secret key |
| Backups | Every night, encrypted and kept off the machine; restores included | The archive of your configuration, and the restore request, when you need one |
| Migration | Your current server migrated, free of charge | The timing of the switch |
If you would rather have our teams work inside the application itself, that service is billed by the hour or at a fixed rate, with an estimate shared before the work starts.
With a Simafri Managed VPS, our teams keep your Glance instance’s server up to date, monitor it day and night and step in without waiting for your call; they also proactively monitor your instance and recommend useful fixes, which you apply, yourself or through your AI assistant. Backups are encrypted every night and kept off the machine, restores are included, and migrating your current server is free.
Yes. Glance is under the AGPL-3.0 license: you can run it for yourself, your family or your team with no license to buy. What remains is the cost of the server that runs it.
Use the glanceapp/glance image in a compose.yaml, mount a config folder on /app/config with your glance.yml in it, publish port 8080 on 127.0.0.1, run docker compose up -d, and put an HTTPS reverse proxy in front.
Yes, since version 0.8. Add an auth block to glance.yml with a secret key generated by secret:make and, for each user, a password hash generated by password:hash. Set proxied: true behind a reverse proxy, so that Glance blocks only the address that fails to sign in five times in five minutes.
No. Glance reloads its configuration file as soon as you save it, and keeps the previous version if the new one has an error. Changes to environment variables, such as the .env file, need docker compose up -d.
Very little. On our test VPS, the Glance container used about 13 MB of memory with a page of four widgets loaded, and its image takes about 11 MB of disk.
Glance keeps no database. Archive its folder: compose.yaml, the .env file with the secret key and the password hash, and the config folder. To restore, extract the archive and run docker compose up -d.
Read the release notes, change the image tag in compose.yaml, then run docker compose pull, docker compose run --rm glance config:validate and docker compose up -d. Glance keeps no data to migrate.
A managed VPS covers the server: system, security, monitoring and backups. Our teams also proactively monitor your instance and recommend useful fixes, which you apply. Work inside the application is billed by the hour or at a fixed rate.
Simafri
Let's talk about your project
Tell us what you need in a few words: we will get back to you quickly.
Thank you! Your request has been sent. We'll get back to you shortly.
Prefer email? Write to us at support@simafri.com.