NewYour coding agent can read the release notes before it upgrades.Set up the MCP server β
Go modules
Go modules, #3086 by repository stars
Latest stable
v0.13.3
Last release 9 months ago
11 Feb 2026
Ships fairly regularly
a new release about every 2 weeks
Most releases are documented
notes for 21 of 26 stable releases
Nothing withdrawn
no release was ever pulled
1 years old
26 releases Β· first in 2025
Drag across the ruler to compare, or tap a release to open it.
You'll probably notice nothing. Under the hood, I've updated the Go toolchain to v1.26.0, Node.js to v25.6.0, and migrated to the new and maintained Y
You'll probably notice nothing. Under the hood, I've updated the Go toolchain to v1.26.0, Node.js to v25.6.0, and migrated to the new and maintained YAML v4 library. These updates bring improved performance, security patches, and keep TraLa running smoothly on the latest and greatest.
Full Changelog: v0.13.2...v0.13.3
Your coding agent can read these notes before it upgrades. Set up the MCP server β
Ever wondered why only 98 services were displayed in your TraLa dashboard, even though you had 203 routers configured? This release finally squashes t
Ever wondered why only 98 services were displayed in your TraLa dashboard, even though you had 203 routers configured? This release finally squashes the long-standing bug (#34) where TraLa was limited to displaying fewer than 100 services due to Traefik's pagination settings. Now, all your services will be displayed correctly, no matter how many you have!
No configuration changes are required! Simply update to this version, and TraLa will automatically fetch all your services from the Traefik API.
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.13.1...v0.13.2
Ever wanted more flexibility in pulling your TraLa image? Now you can! I've added Docker Hub as a secondary registry alongside GitHub Container Regist
Ever wanted more flexibility in pulling your TraLa image? Now you can! I've added Docker Hub as a secondary registry alongside GitHub Container Registry, giving you backup options for deployments. Plus, a sneaky bug in icon fetching for redirected services has been squashed.
Pull from Docker registry:
services:
trala:
# Secondary (Docker Hub)
image: dannybouwers/trala:latest
The icon fix is automatic - no configuration needed. Services behind redirects will now display their icons correctly.
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.13.0...v0.13.1
Ever been frustrated by SSL certificate errors when connecting to the Traefik API over the Docker network? I've got you covered! With this release, yo
Ever been frustrated by SSL certificate errors when connecting to the Traefik API over the Docker network? I've got you covered! With this release, you can now allow insecure connections to the Traefik API, making it easier to use TraLa in environments where redirects to HTTPS are configured on all entrypoints.
Update your configuration.yml file to include the new setting:
environment:
traefik:
api_host: http://traefik:8080
enable_basic_auth: true
insecure_skip_verify: true # Skip SSL certificate verification for Traefik API (default: false)
Or use the environment variable:
services:
trala:
image: ghcr.io/dannybouwers/trala:latest
environment:
TRAEFIK_INSECURE_SKIP_VERIFY: "true"
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.12.0...v0.13.0
Ever felt like a group with just one service is a bit... lonely? Well, now you can set the minimum number of services required to form a group! No mor
Ever felt like a group with just one service is a bit... lonely? Well, now you can set the minimum number of services required to form a group! No more "groups" that are just a single service hanging out by itself. Or, if you prefer, you can now allow single-service groups to form - because sometimes even a solo service deserves its own group!
Update your configuration.yml file to include the new setting:
environment:
grouping:
enabled: true
columns: 3
tag_frequency_threshold: 0.9
min_services_per_group: 2 # Minimum number of services required for a tag to form a group (default: 2)
Or use the environment variable:
services:
trala:
image: ghcr.io/dannybouwers/trala:latest
# ... your existing TraLa configuration ...
environment:
GROUPING_MIN_SERVICES_PER_GROUP=2
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.11.1...v0.12.0
Thanks to Ethan Sholly, the owner of selfh.st, who provided a custom integration for TraLa, I could simplify and make tag fetching more robust. You pr
Thanks to Ethan Sholly, the owner of selfh.st, who provided a custom integration for TraLa, I could simplify and make tag fetching more robust. You probably won't notice anything, but under the hood, the application now handles tags more efficiently and reliably.
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.11.0...v0.11.1
Tired of scrolling through a long list of services? With the new smart grouping feature, TraLa now automatically organizes your services into logical
Tired of scrolling through a long list of services? With the new smart grouping feature, TraLa now automatically organizes your services into logical groups based on their tags from selfh.st/apps. No more clutter - just a clean, organized dashboard! And off course with the option to manually override it.
Smart grouping analyzes your service tags and configurations to create meaningful categories. For example, services with similar tags will be grouped together, and you can manually assign services to specific groups using the group field in service overrides. Groups can be collapsed or expanded individually via the frontend toggle.
grouping.enabled setting in your configuration file or the GROUPING_ENABLED environment variable.grouping.columns or GROUPED_COLUMNS.grouping.tag_frequency_threshold or GROUPING_TAG_FREQUENCY_THRESHOLD.group field of service overrides.version: 3.1
# Service configuration
services:
# Smart grouping settings
grouping:
enabled: true
columns: 3 # Number of columns in grouped view (1-6), default: 3
tag_frequency_threshold: 0.9 # Threshold for excluding tags present in more than 90% of services
# Service overrides for display names, icons, and groups
overrides:
- service: "unifi-controller"
display_name: "UniFi Network"
icon: "ubiquiti-unifi.svg"
group: "Network"
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.10.1...v0.11.0
You'll probably notice nothing. Dependancy's updated.
You'll probably notice nothing. Dependancy's updated.
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.10.0...v0.10.1
> Breaking changes - update your configuration file
[!WARNING]
Breaking changes - update your configuration file
If you use multiple entry points, e.g. one public and one local, you can now exclude all services based on the entry point name. You need to update your configuration file to version 3.0. Also if you don't use this method.
In addition to excluding based on service name, you can exclude services based on their entrypoint names using the exclude.entrypoints key. This allows you to hide entire categories of services (e.g. internal-only or admin interfaces) by filtering on the Traefik entrypoint they use.
# Service configuration
services:
# Services to exclude from the dashboard
exclude:
routers:
- "traefik-api" # Hide the Traefik API itself
- "admin-panel" # Hide internal admin interface
- "api*" # Hide all routers starting with "api"
entrypoints:
- "*lan*" # Hide services using entrypoints containing "lan"
- "internal" # Hide services using the "internal" entrypoint
To fix your existing configuration, add the key routers: one level below services: and move the list of services to that key. Update the config version to version: 3.0 to remove the front-end warning.
Version 2.0:
# Service configuration
services:
# Services to exclude from the dashboard
exclude:
- "traefik-api"
- "admin-panel"
- "api*"
Version 3.0
# Service configuration
services:
# Services to exclude from the dashboard
exclude:
routers: # β οΈ NEW KEY
- "traefik-api"
- "admin-panel"
- "api*"
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.9.1...v0.10.0
Very boring update: a backend dependency bumped to a new version. You'll probably notice nothing.
Very boring update: a backend dependency bumped to a new version. You'll probably notice nothing.
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.9.0...v0.9.1
With this version you can select the frontend language using the language parameter. You can now have a frontend in German or Dutch (next to the defau
With this version you can select the frontend language using the language parameter. You can now have a frontend in German or Dutch (next to the default English). Please create a PR if you would like to add another translation!
Next to that: fixes and updates.
The application's language can be configured either through the LANGUAGE environment variable or the configuration.yml file.
# Environment settings (optional, environment variables take precedence)
environment:
language: nl # change Language (Default "en").
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.8.0...v0.9.0
For everyone as lazy as me, @M1scer added the option to exclude more services with one line; you can now use wildcards (. and *) in the list of servic
For everyone as lazy as me, @M1scer added the option to exclude more services with one line; you can now use wildcards (. and *) in the list of services to exclude.
If you're looking for more security, TraLa now supports basic authentication on the Traefik API thanks to @PhilipJonasFranz . This way you can make sure the API exposing your stack is only accessible by TraLa.
The full instructions are added to the README. In short:
Add basic auth to the Traefik API by inserting a basic auth middleware into the router that exposes the API.
Enable basic auth in the configuration file or environment variables. I'd recommend using the config file and docker secrets, but more options are possible.
Docker compose:
services:
traefik:
# ... your existing Traefik configuration ...
labels:
# Define the basic auth username and hashed password
- "traefik.http.middlewares.traefik-api-auth.basicauth.users=<REPLACE_ME>"
# API
# ...
- "traefik.http.routers.traefik-api.middlewares=traefik-api-auth"
trala:
# ... your existing TraLa configuration ...
secrets:
- basic_auth_password
secrets:
basic_auth_password:
file: ./basic_auth_password.txt
TraLa Configuration:
environment:
traefik:
basic_auth:
username: <USERNAME>
password_file: /run/secrets/basic_auth_password
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.7.0...v0.8.0
> Breaking changes - update your configuration file
[!WARNING]
Breaking changes - update your configuration file
This release gives you more power over the dashboard. You can now override the names of services. You can also manually add services not managed by Traefik. The only downside: I had to make some breaking changes to the config file. (Fortunately, the app will check compatibility and warn you!)
The section icons: isn't part of the config file anymore. It's moved to services:. You can just copy-paste it since the structure is fully compatible. Once moved, change the version number to version: 2.0.
You can override the service name using the attribute display_name. This name will be shown in the frontend and will be used to search for icons.
# TraLa Configuration File
# Version 2.0
version: 2.0
# Service configuration
services:
# Service overrides for display names and icons
overrides:
# Override both display name and icon
- service: "firefly-core"
display_name: "Firefly III"
icon: "https://cdn.jsdelivr.net/gh/selfhst/icons/svg/firefly-iii.svg"
Sometimes you want to add services to your dashboard that aren't managed by Traefik - like external websites, cloud services, or resources hosted elsewhere. TraLa allows you to manually add these services through the configuration file.
Manual services are defined in the manual section of your configuration.yml file. These services:
Each manual service can include:
name: The display name (required)url: The URL of the service (required)icon: Custom icon (optional - full URL or filename from selfh.st)priority: Priority for sorting (optional - higher numbers appear first, default: 50)# TraLa Configuration File
# Version 2.0
version: 2.0
# Service configuration
services:
# Manually added services (not from Traefik)
manual:
# Basic manual service with just name and URL
- name: "Reddit"
url: "https://www.reddit.com"
# Manual service with custom icon
- name: "GitHub"
url: "https://github.com"
icon: "github.svg"
# Manual service with icon and priority
- name: "The Verge"
url: "https://www.theverge.com"
icon: "https://www.theverge.com/favicon.ico"
priority: 100
# Manual service with just name, URL, and priority (icon will be auto-detected)
- name: "Hacker News"
url: "https://news.ycombinator.com"
priority: 90
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.6.0...v0.7.0
A small icon in the search bar now shows which search engine you have configured. Also changed the placeholder text to clarify the search bar can also
A small icon in the search bar now shows which search engine you have configured. Also changed the placeholder text to clarify the search bar can also be used to search the web.
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.5.2...v0.6.0
Some nerdy enhancements. The main thing you will notice, is the version number in the lower right corner of the dashboard. In the background you can f
Some nerdy enhancements. The main thing you will notice, is the version number in the lower right corner of the dashboard. In the background you can find a health check on the container and the Tailwind Playground CDN warning in the browser console is gone.
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.5.1...v0.5.2
The user is more important than the alphabet. π TraLa only uses the first URL it can build if more options are specified. Then it should have used the
The user is more important than the alphabet. π TraLa only uses the first URL it can build if more options are specified. Then it should have used the options in the order the user specifies, not alphabetical. It does now!
Technical details: if a router had multiple entryPoints specified, TraLa will build a URL based on the first entry point specified in the configuration for that router (no longer the one with the name sorted to first place).
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.5.0...v0.5.1
Want to go offline? Use some exclusive icons? As of this version you can! Mount a directory with icons to the container and TraLa will use the same se
Want to go offline? Use some exclusive icons? As of this version you can! Mount a directory with icons to the container and TraLa will use the same search logic to find the right icon in your personal library as it does to find an icon on self.st/icons.
version: '3.8'
services:
trala:
image: ghcr.io/dannybouwers/trala:latest
# ... your existing traefik configuration ...
volumes:
# Mount a directory with custom icons. See "Configuration" section below.
- ./icons:/icons:ro
# ...
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.4.0...v0.5.0
> Breaking changes - replace your configuration files
[!WARNING]
Breaking changes - replace your configuration files
This version unifies the two configuration files to one and add the option to fully configure TraLa using a single YAML file.
In order for your setup to work, manually merge the files icon_overrides.yml and services.yml to a file mounted as configuration.yml. Please refer to the readme for the details on the new structure.
--api.insecure=trueFull Changelog: https://github.com/dannybouwers/trala/compare/v0.3.1...v0.4.0
Thanks to @PhilipJonasFranz automatic icon search is now case insensitive.
Thanks to @PhilipJonasFranz automatic icon search is now case insensitive.
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.3.0...v0.3.1
URLs and more file extensions in icon_overrides.yml
icon_overrides.ymlservices.ymlYou can map this router name to either:
When using a filename from the selfh.st icon repository, you can specify files with the following extensions:
You can hide specific services from appearing in the dashboard by specifying their router names in a services.yml configuration file. This is useful for hiding administrative interfaces or services you don't want to be easily accessible through the dashboard.
The application uses the router name from your Traefik configuration (the part before the @) to identify services. By adding router names to the exclusion list, those services will not be processed or displayed in the dashboard.
services.ymlCreate a file named services.yml on your Docker host.
Use the following YAML format:
# services.yml
# Format: List router names to exclude from the dashboard
service:
exclude:
# Example 1: Exclude the Traefik API router
- traefik-api
# Example 2: Exclude a private admin interface
- private-admin-panel
Mount this file into the container at /config/services.yml using a volume, as shown in the docker-compose.yml example.
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.2.5...v0.3.0
No new features, simply did some chores. All dependancies are up to date again.
No new features, simply did some chores. All dependancies are up to date again.
Full Changelog: https://github.com/dannybouwers/trala/compare/v0.2.4...v0.2.5
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per month.