This is two related requests; let me know if you'd prefer them as separate issues
Root redirect
Currently, the root of the tracking domain redirects to my separate admin domain:
example.com → admin.example.com
I'd like to be able to configure the redirect for the root route. I'm using rushomon for my own personal use, so I'd prefer not to send visitors to the landing page.
Similar platforms use an empty slug for a link to denote the root redirect, but currently that triggers auto-generation of a slug in rushomon. Maybe a checkbox for "Root path" would be necessary.
404 / non-existing slug
Currently, visiting a path that hasn't been created also redirects to my separate admin domain, though seemingly tries to land on a 404 page in between that doesn't actually appear.
example.com → admin.example.com/404 → admin.example.com
I'd like to be able to configure the redirect for 404s and manage it as a link. If this hasn't been configured, default behavior should be to land on a generic 404 page (some platforms allow customizing that page with CSS and such, but that would be a separate request).
I'd suggest that * be the slug for this link which would act as a "wildcard fallback".
Question: the destination would obviously have its own response status, but should this have an option for customizing whether 404 is returned vs usual redirect codes like 307? This could be useful as both a 404 not found as well as essentially a fallback redirect where the admin doesn't consider it an error.
This is two related requests; let me know if you'd prefer them as separate issues
Root redirect
Currently, the root of the tracking domain redirects to my separate admin domain:
example.com → admin.example.comI'd like to be able to configure the redirect for the root route. I'm using rushomon for my own personal use, so I'd prefer not to send visitors to the landing page.
Similar platforms use an empty slug for a link to denote the root redirect, but currently that triggers auto-generation of a slug in rushomon. Maybe a checkbox for "Root path" would be necessary.
404 / non-existing slug
Currently, visiting a path that hasn't been created also redirects to my separate admin domain, though seemingly tries to land on a 404 page in between that doesn't actually appear.
example.com → admin.example.com/404 → admin.example.comI'd like to be able to configure the redirect for 404s and manage it as a link. If this hasn't been configured, default behavior should be to land on a generic 404 page (some platforms allow customizing that page with CSS and such, but that would be a separate request).
I'd suggest that
*be the slug for this link which would act as a "wildcard fallback".Question: the destination would obviously have its own response status, but should this have an option for customizing whether 404 is returned vs usual redirect codes like 307? This could be useful as both a 404 not found as well as essentially a fallback redirect where the admin doesn't consider it an error.