Hands-off Docker discovery. 3.1.0 taught Muximux to read your Docker daemon and import containers as apps with one click. 3.2.0 can do it automatically.
Label a container, and it just appears
If you already label your containers with the muximux.* keys (name, icon, group, port, proxy, even a gateway subdomain), Muximux can now pick them up on its own. Set one flag and a labeled container shows up in your dashboard without ever opening the Discover modal. It is built for a GitOps workflow: declare an app in your compose file, deploy, and it is there.
You choose how far it goes, with discovery.docker.auto_import (or the MUXIMUX_DISCOVERY_AUTO_IMPORT environment variable):
off(the default) keeps today's behavior: labels are suggestions, you import by hand.addimports a new labeled container once and then leaves it alone.updatealso keeps the app's fields in sync as you change labels.syncis the full mirror: it adds, updates, and removes apps to match your labeled containers exactly.
It is off by default and on purpose. Turning it on means every labeled container on your Docker host enters your config with no review step, including any that publish a public HTTPS subdomain, so only you as the host operator can enable it.
A few things make it safe to live with: Muximux only ever manages the apps it imported (your hand-added apps are never touched), editing an auto-imported app's URL in the UI detaches it so your change wins, and muximux.app.enabled=false lets a single container opt out. The full reference, including the security note, is on the Docker discovery wiki page.
Upgrading
Drop-in, nothing to migrate, and nothing changes until you opt in. Pull the latest image (ghcr.io/mescon/muximux) or download the new binary for your platform from the assets below, then restart.
Find a bug? Please open an issue. Enjoy!