files-api.novox.be and files.novox.be worked earlier tonight from route-adapter-generated files, but minio's module.json on main never actually carried a route requirement — that capability has been sitting in PR #58 the whole time, bundled with an unrelated network rename and console redirect URL that need their own calmer review. This is just the two routes: requires: route, contributes.route.api/.console (ContributesMany, proven working via mesh-controller #55/#57), and the console port (9001) actually published and declared in listens.
Found assigning route-proxy for the first time tonight: its own routes file, generated the identical way route-adapter's always was, had four hostnames in it instead of six — nothing served files-api/files at all, which would have been a real, silent outage the moment Traefik stopped.
`files-api.novox.be` and `files.novox.be` worked earlier tonight from route-adapter-generated files, but minio's `module.json` on main never actually carried a route requirement — that capability has been sitting in PR #58 the whole time, bundled with an unrelated network rename and console redirect URL that need their own calmer review. This is just the two routes: `requires: route`, `contributes.route.api`/`.console` (ContributesMany, proven working via mesh-controller #55/#57), and the console port (9001) actually published and declared in `listens`.
Found assigning route-proxy for the first time tonight: its own routes file, generated the identical way route-adapter's always was, had four hostnames in it instead of six — nothing served files-api/files at all, which would have been a real, silent outage the moment Traefik stopped.
files-api.novox.be and files.novox.be worked earlier tonight from route-
adapter-generated files, but minio's module.json on main never actually
carried a route requirement — that capability has been sitting in PR #58
the whole time, bundled with an unrelated network rename and console
redirect URL that need their own calmer review. This is just the two
routes: requires: route, contributes.route.api/.console (ContributesMany,
proven working via mesh-controller #55/#57), and the console port (9001)
actually published and declared in listens.
Found assigning route-proxy for the first time tonight: its own routes
file, generated the identical way route-adapter's always was, had four
hostnames in it instead of six — nothing served files-api/files at all,
which would have been a real, silent outage the moment Traefik stopped.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
files-api.novox.beandfiles.novox.beworked earlier tonight from route-adapter-generated files, but minio'smodule.jsonon main never actually carried a route requirement — that capability has been sitting in PR #58 the whole time, bundled with an unrelated network rename and console redirect URL that need their own calmer review. This is just the two routes:requires: route,contributes.route.api/.console(ContributesMany, proven working via mesh-controller #55/#57), and the console port (9001) actually published and declared inlistens.Found assigning route-proxy for the first time tonight: its own routes file, generated the identical way route-adapter's always was, had four hostnames in it instead of six — nothing served files-api/files at all, which would have been a real, silent outage the moment Traefik stopped.