Static configuration limits hot-reload for entrypoint ports in Traefik dev environment

Goal

Enable a repeatable local development workflow where changes to Traefik entrypoint settings (such as the port number) are applied without restarting the Traefik process.

Constraints and uncertainty

According to the Traefik reference, entrypoint definitions belong to the static configuration layer, which is read only at process start and is not hot‑reloaded by file or Docker providers. This means that editing the static file does not take effect until the container is restarted, breaking an edit‑and‑reload loop. The alternative is to treat entrypoint details as dynamic configuration, but the documentation does not provide a supported method for doing so, leaving the placement decision unresolved.

Can entrypoint values be defined via dynamic configuration instead of static? What are the trade‑offs of expressing entrypoint details through container labels or middleware? Is there a supported way to trigger a reload of entrypoint changes without restarting Traefik?