Replacing existing file mount with RouteGroup

Branching off of this thread on co-branding

I was testing some hacky things out in trying to customize the username and password entry view that is currently provided the co-branding.css file directly, and doesn’t implement theming the way that the other sign in views do. What this means, is you can’t customize that view in the same way you can the rest, only the provided (and supported) colors.

Disclaimer: I am aware this is likely unsupported behavior, however I have become curious now after the amount of effort I have put in, and Im just innately curious how to solve this challenge. lol

In my testing I see that its provided the css file directly from /data/co-branding/co-branding.css. So my first attempt was to replace the route group mounted, by creating a module with the id of co-branding and then mounting a new file at /co-branding.css.

It seems that if I set the module id to something different like co-brandings then everything works as expected, but the co-branding route is explicitly blocked from creating a new route (Even with a different file name i.e. /hello-world.)

Is there something implicitly blocking the replacement of this file in that route group and my efforts are futile? I wouldn’t be surprised if that’s the case, as like I said, likely unsupported territory.


A single servlet is attached to a single route at the module id level. There’s no co-existence possible unless the one servlet itself has a hook for that.

Not that you can’t override what you wish if you deploy behind nginx or a similar reverse proxy.

1 Like