v0.7.9

Another small release that's primarily focused around custom-api widget improvements.

Changed

You no longer need to convert numbers to float before doing math operations with them. When adding two integers together, the result will be an integer. Adding two floats together or an integer and a float will result in a float.

Before:

{{ (add (.JSON.Int "foo" | toFloat) (.JSON.Int "bar" | toFloat)) | toInt }}

Now:

{{ add (.JSON.Int "foo") (.JSON.Int "bar") }}

(this is consistent for all math operations, not just addition)

New

skip-json-validation and .JSONLines

- type: custom-api
  url: https://api.example.com
  skip-json-validation: true

Some API's return newline separated JSON objects instead of a single JSON array. This is not valid JSON, so the custom-api widget will fail to parse it. You can now set skip-json-validation to true to skip the validation step and parse the response as a list of JSON objects within your template.

{"name": "Steve", "age": 30}
{"name": "Alex", "age": 25}
{"name": "John", "age": 35}

You can then access the JSON objects using .JSONLines:

{{ range .JSONLines }}
  {{ .String "name" }}
{{ end }}

New functions

concat

{{ concat "foo" "bar" "baz" }}

will return foobarbaz.

(thanks @ralphocdol)

now

Returns the current time as a time.Time object.

{{ now }}
{{ now.Hour }}:{{ now.Minute }}:{{ now.Second }}
{{ now.Unix }}

2025-03-29 17:20:18.4905224 +0000 GMT m=+376.954385401
17:20:18
1743268818

This can also be used to convert time to your current timezone:

{{ $parsedTime := .JSON.String "date_created" | parseTime "rfc3339" }}
{{ $created := $parsedTime.In now.Location }}
{{ $created.Hour }}:{{ $created.Minute }}:{{ $created.Second }}

(thanks @not-first & @ralphocdol)

offsetNow

Returns the current time offset by a given amount:

{{ offsetNow "1h" }}
{{ now }}
{{ offsetNow "-1h" }}

2025-03-29 18:44:04.2719241 +0000 GMT m=+4178.324981601
2025-03-29 17:44:04.2719241 +0000 GMT m=+578.324981601
2025-03-29 16:44:04.2719241 +0000 GMT m=-3021.675018399

This can be used to check if something happened within a certain time frame:

{{ $created := .JSON.String "date_created" | parseTime "rfc3339" }}
{{ if ($created.After (offsetNow "-1h")) }}
  Created less than 1 hour ago
{{ end }}

Widget-Title-URL header for extension widget

The extension widget can now return a Widget-Title-URL header to set the link of the widget's title if it has not already been set by the user.

(thanks @not-first)

Fixes

• The markets widget will now properly display prices of markets where the price is less than 0.01 (thanks @nsdont)

v0.7.8

The custom-api widget has received a lot of positive feedback since its introduction in v0.7.0. Many people have made and shared their own widgets over at the new community-widgets repository as well as the Discord server. This release includes many improvements based on feedback from the community that will make it even more capable and easier to use.

New

Insecure requests

You can now allow insecure requests (those to APIs behind a self-signed certificate) via a allow-insecure property:

- type: custom-api
  url: https://api.example.com
  allow-insecure: true

(thanks @ralphocdol)

Parameters

You can now specify query parameters via a parameters property:

- type: custom-api
  url: https://api.example.com
  parameters:
    foo: bar
    baz: qux

Note

Using the parameters property will override any query parameters specified in the URL.

(thanks @ralphocdol)

Request method and body

You can now specify the request method and body via the method, body-type and body properties:

- type: custom-api
  url: https://api.example.com
  method: POST
  body-type: json
  body:
    foo: bar
    baz: qux

If you set a body, the method will automatically be set to POST and the body-type will be set to json, so you don't have to specify them explicitly.

- type: custom-api
  url: https://api.example.com
  body-type: string
  body: |
    foo=bar&baz=qux

(thanks @not-first)

Subrequests

You can now make multiple requests in a single custom-api widget via a subrequests property:

- type: custom-api
  url: https://api.example.com
  subrequests:
    another-one:
      url: https://api.example.com/another-one
    and-another-one:
      url: https://api.example.com/and-another-one

Subrequests can take all of the same properties as the main request, such as: parameters, headers, method, body-type, body and allow-insecure.

To access the JSON of a subrequest, you can use .Subrequest "key":

<p>{{ (.Subrequest "another-one").JSON.String "foo" }}</p>

This can get cumbersome to write if you need to reference the subrequest in multiple places, so you can instead assign it to a variable:

{{ $anotherOne := .Subrequest "another-one" }}
<p>{{ $anotherOne.JSON.String "foo" }}</p>
<p>{{ $anotherOne.JSON.Int "bar" }}</p>

You can also access the response as you would on the main request:

{{ $andAnotherOne := .Subrequest "and-another-one" }}
<p>{{ $andAnotherOne.Response.StatusCode }}</p>

(thanks @ralphocdol)

New functions

trimPrefix

{"foo": "bazbar"}

<p>{{ .JSON.String "foo" | trimPrefix "baz" }}</p>

<p>bar</p>

trimSuffix

{"foo": "barbaz"}

<p>{{ .JSON.String "foo" | trimSuffix "baz" }}</p>

<p>bar</p>

trimSpace

{"foo": "  bar  "}

<p>{{ .JSON.String "foo" | trimSpace }}</p>

<p>bar</p>

replaceAll

{"foo": "barbazbar"}

<p>{{ .JSON.String "foo" | replaceAll "baz" "bar" }}</p>

<p>barbarbar</p>

findMatch

{"foo": "bar-123456-baz"}

<p>{{ .JSON.String "foo" | findMatch "\\d+" }}</p>

The pattern is a regular expression, although note that backslashes need to be escaped, so \d in a normal regular expression would be \\d here.

<p>123456</p>

findSubmatch

{"foo": "bar-unknown-value"}

<p>{{ .JSON.String "foo" | findSubmatch "bar-(.*)" }}</p>

The pattern is a regular expression, and only the first submatch is returned.

<p>unknown-value</p>

parseTime

{"foo": "2021-01-02T15:04:05Z"}

{{ $parsedTime := .JSON.String "foo" | parseTime "rfc3339" }}
<p>Year: {{ $parsedTime.Year }}</p>
<p>Month: {{ $parsedTime.Month }}</p>
<p>Day: {{ $parsedTime.Day }}</p>
<p>Hour: {{ $parsedTime.Hour }}</p>
<p>Minute: {{ $parsedTime.Minute }}</p>
<p>Second: {{ $parsedTime.Second }}</p>

Other accepted time formats are unix, rfc3339nano, datetime, dateonly or a custom format using Go's date formatting. The returned object is Go's time.Time.

<p>Year: 2021</p>
<p>Month: January</p>
<p>Day: 2</p>
<p>Hour: 15</p>
<p>Minute: 4</p>
<p>Second: 5</p>

toRelativeTime

{"foo": "2021-01-02T15:04:05Z"}

<p {{ .JSON.String "foo" | parseTime "rfc3339" | toRelativeTime }}></p>

Note

The return value of this function must be placed within a tag's attributes, not within its content.

<p data-dynamic-relative-time="1609602245"></p>

This will automatically be converted to 1d, 2h, etc. on the client side.

parseRelativeTime

This is just a shorthand for parsing time and converting it to relative time. Instead of:

<p {{ .JSON.String "foo" | parseTime "rfc3339" | toRelativeTime }}></p>

You can simply do:

<p {{ .JSON.String "foo" | parseRelativeTime "rfc3339" }}></p>

sortByString, sortByInt, sortByFloat, sortByTime

{"students": [
  {"name": "Bob", "age": 20},
  {"name": "Alice", "age": 30},
  {"name": "Charlie", "age": 10}
]}

{{ range .JSON.Array "students" | sortByString "name" "asc" }}
  <p>{{ .String "name" }}</p>
{{ end }}

<p>Alice</p>
<p>Bob</p>
<p>Charlie</p>

---

{{ range .JSON.Array "students" | sortByInt "age" "desc" }}
  <p>{{ .Int "age" }}</p>
{{ end }}

<p>30</p>
<p>20</p>
<p>10</p>

---

{"students": [
  {"name": "Bob", "gpa": 3.5},
  {"name": "Alice", "gpa": 4.0},
  {"name": "Charlie", "gpa": 2.0}
]}

{{ range .JSON.Array "students" | sortByFloat "gpa" "asc" }}
  <p>{{ .Float "gpa" }}</p>
{{ end }}

<p>2</p>
<p>3.5</p>
<p>4</p>

---

{"students": [
  {"name": "Bob", "dob": "2000-01-01"},
  {"name": "Alice", "dob": "1990-01-01"},
  {"name": "Charlie", "dob": "2010-01-01"}
]}

{{ range .JSON.Array "students" | sortByTime "dob" "dateonly" "asc"  }}
  <p>{{ .String "name" }}</p>
{{ end }}

Here, dateonly is the same format that you would use with parseTime.

<p>Alice</p>
<p>Bob</p>
<p>Charlie</p>

Other additions

Extension widget headers property

You can now specify headers in the extension widget:

- type: extension
  headers:
    Authorization: Bearer token

Fixes

• Fixed being unable to parse an empty response body in the custom-api widget
• Fixed always overriding query parameters in the extension widget, they will now only be overridden if the parameters property is set

v0.7.7

What's changed

• Improved accessibility of the Docker containers widget (thanks @Lanie-Carmelo)
• Reduced the contrast of calendar dates to better match the design language of other widgets
• Added more info to error messages of DNS stats widget when using service: pihole-v6 to help with debugging issues
• Changed the integer type in the Custom API widget to int from int64 so that you can now perform calculations on the result of the len function (thanks @titembaatar)

Fixed

• Videos widget with style vertical-list not opening links in new tab (thanks @aliaghil)
• DNS stats widget "Top blocked domains" in the UI having an additional triangle on the left on Safari (thanks @lukpep)

v0.7.6

Fixed an issue with the previous release for the DNS stats widget when using service: pihole-v6

v0.7.5

What's Changed

Added support for Pi-hole version 6 via:

- type: dns-stats
  service: pihole-v6
  url: ${PIHOLE_URL}
  password: ${PIHOLE_PASSWORD}

(thanks to @KallanX and @ralphocdol)

Where ${PIHOLE_PASSWORD} is either the admin dashboard password or the application password which can be created from:

Settings -> Web Interface / API -> Configure app password

v0.7.4

What's Changed

• Made a number of accessibility improvements that should hopefully make Glance available to a wider audience

Fixed

• Currency symbol not being properly set for some markets (thanks @hkrob)

New Contributors

• @DavisYe made their first contribution in #372
• @legoraft made their first contribution in #382
• @KadoBOT made their first contribution in #399

v0.7.3

Fixed

• Config auto reload not working when editing with Vim (thanks @rubiojr)
• Markets widget rate limit error (thanks @ChezOps)

Changed

• Increased docker containers widget timeout (thanks @wagwan-piffting-blud)
• No longer shows errors in the console when trying to get sensors data for server stats widget on OpenBSD (thanks @WickedShell)

v0.7.2

New

• Added hide-mountpoints-by-default property to the server-stats widget

Fixed

• Potential fix for crash on OpenBSD when using server-stats widget
• Fixed URL of Dashboard Icons to point to new repository
• Fixed small visual glitch with the popover functionality

v0.7.1

Fixed an error when using the new playlists property in the videos widget (thanks corbin)

v0.7.0

Jump to section

• Docker container breaking changes
• CLI breaking changes
• New widgets
  • Docker containers
  • Custom API
  • Server stats
  • Split column
  • Calendar (reworked)
• New features
  • Auto reload on config change
  • Environment variables anywhere in the config
  • Include files in the config
  • Custom HTML in document <head>
  • Support for selfh.st and Dashboard icons
• New styles
  • [Monitor] compact
  • [Videos] vertical-list
• Widget enhancements
  • [Twitch channels] stream preview on hover
  • [RSS] request headers, limit per feed, preserve-order
  • [Videos] playlists
  • [Group] support for title-url
  • [Monitor] alt-status-codes, error-url
  • [Extension] specify if content should have no frame
  • [Bookmarks] target for links, same-tab and hide-arrow for groups
  • [Reddit] proxy
  • [Search] placeholder and clear input on search
  • [Markets] chart-link-template, symbol-link-template and sort-by
  • [Releases] include-prereleases
  • [DNS stats] hide-graph, hide-top-domains and allow-insecure
  • [Clock] now displays exact time difference for timezones
• Fixes
• Been a while
• Community overhaul
• Thank you

Docker container breaking changes

Until now, setting up Glance using its Docker container involved a somewhat unusual step where the config file was solely mounted as a volume. This tripped up some users and caused unnecessary confusion due to a few odd behaviors.

The default location of the config file has now been changed to /app/config/glance.yml from /app/glance.yml. That means your docker-compose.yml file should now look like the following:

services:
  glance:
    image: glanceapp/glance
    volumes:
      - ./config:/app/config

This also requires that you place your glance.yml file in a config directory in the same location as your docker-compose.yml file. If you're unsure what changes you need to make, there is an upgrade guide available here as well as a new recommended docker compose directory structure available here.

CLI breaking changes

Previously, you could run the following to validate your config file without starting Glance:

glance --config /path/to/config.yml --check-config

For the sake of consistency with the few new added comands (and because this shouldn't have been a flag in the first place), this has now been changed to:

glance --config /path/to/config.yml config:validate

New widgets

Docker containers

Display the status of your Docker containers along with an icon and an optional short description.

- type: docker-containers
  hide-by-default: false

Note

The widget requires access to docker.sock. If you're running Glance inside a container, this can be done by mounting the socket as a volume:

services:
  glance:
    image: glanceapp/glance
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

Configuration of the containers is done via labels applied to each container:

  jellyfin:
    image: jellyfin/jellyfin:latest
    labels:
      glance.name: Jellyfin
      glance.icon: si:jellyfin
      glance.url: https://jellyfin.domain.com
      glance.description: Movies & shows

For services with multiple containers you can specify a glance.id on the "main" container and glance.parent on each "child" container:

View docker-compose.yml

services:
  immich-server:
    image: ghcr.io/immich-app/immich-server
    labels:
      glance.name: Immich
      glance.icon: si:immich
      glance.url: https://immich.domain.com
      glance.description: Image & video management
      glance.id: immich

  redis:
    image: docker.io/redis:6.2-alpine
    labels:
      glance.parent: immich
      glance.name: Redis

  database:
    image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0
    labels:
      glance.parent: immich
      glance.name: DB

  proxy:
    image: nginx:stable
    labels:
      glance.parent: immich
      glance.name: Proxy

This will place all child containers under the Immich container when hovering over its icon:

If any of the child containers are down, their status will propagate up to the parent container:

(thanks @baranovskis & @reality-exe, inspired by https://github.com/DVDAndroid/glance-docker-container-ext)

Custom API

Display data from any JSON API in an entirely customizable template.

Note

With great power come great requirements.

The configuration of this widget requires some basic knowledge of programming, HTML, CSS, the Go template language and Glance-specific concepts.

View glance.yml

- type: custom-api
  title: Random Fact
  cache: 6h
  url: https://uselessfacts.jsph.pl/api/v2/facts/random
  template: |
    <p class="size-h4 color-paragraph">{{ .JSON.String "text" }}</p>

View glance.yml

- type: custom-api
  title: Immich stats
  cache: 1d
  url: https://${IMMICH_URL}/api/server/statistics
  headers:
    x-api-key: ${IMMICH_API_KEY}
    Accept: application/json
  template: |
    <div class="flex justify-between text-center">
      <div>
          <div class="color-highlight size-h3">{{ .JSON.Int "photos" | formatNumber }}</div>
          <div class="size-h6">PHOTOS</div>
      </div>
      <div>
          <div class="color-highlight size-h3">{{ .JSON.Int "videos" | formatNumber }}</div>
          <div class="size-h6">VIDEOS</div>
      </div>
      <div>
          <div class="color-highlight size-h3">{{ div (.JSON.Int "usage" | toFloat) 1073741824 | toInt | formatNumber }}GB</div>
          <div class="size-h6">USAGE</div>
      </div>
    </div>

View glance.yml

- type: custom-api
  title: Steam Specials
  cache: 12h
  url: https://store.steampowered.com/api/featuredcategories?cc=us
  template: |
    <ul class="list list-gap-10 collapsible-container" data-collapse-after="5">
    {{ range .JSON.Array "specials.items" }}
      <li>
        <a class="size-h4 color-highlight block text-truncate" href="https://store.steampowered.com/app/{{ .Int "id" }}/">{{ .String "name" }}</a>
        <ul class="list-horizontal-text">
          <li>{{ div (.Int "final_price" | toFloat) 100 | printf "$%.2f" }}</li>
          {{ $discount := .Int "discount_percent" }}
          <li{{ if ge $discount 40 }} class="color-positive"{{ end }}>{{ $discount }}% off</li>
        </ul>
      </li>
    {{ end }}
    </ul>

(thanks @reality-exe)

Server stats

There are other projects dedicated to providing this kind of functionality and this is not meant to be a replacement for any of them, it's intended for people who just want the most basic information about their server without setting up a separate monitoring solution. Things will get improved based on feedback, but the goal is to keep it simple and minimal. If you're looking for a more feature-rich server monitoring solution, Beszel looks like a good choice. With that out of the way:

- type: server-stats
  servers:
    - type: local
      name: Services
      # optionally override the sensor used to determine CPU temperature
      # cpu-temp-sensor: thermal_zone0

      # optionally hide swap
      # hide-swap: true

      # optionally hide or rename mountpoints
      # mountpoints:
      #   "/boot/efi":
      #     hide: true
      #     name: EFI

There's a bunch of bars and their purpose might not be immediately obvious:

• CPU - 1m and 15m average load
• RAM - RAM and SWAP
• Disk – the two mountpoints with the highest usage percentages

If your CPU is feeling a little spicy (assuming Glance was able to determine your CPU sensor) and reaches >=80°C, you'll see a little flame icon next to it. The progress indicators will also turn red (or the equivalent of your negative color) to hopefully grab your attention if anything is unusually high:

![server-stats-preview-1](https://github.com/user-attachments/assets/40597baf-e6e6-4d9c-be3b...