Redirect all frontend routes to start-instance until configured about wildebeest HOT 5 CLOSED

I intentially didn't do it to avoid adding a D1 query on all requests.

from wildebeest.

But don't we hit D1 on every frontend UI request anyway? Especially now that we are reading the thumbnail etc from the DB?
In the data loader for access the instance-config, we could trigger a redirect if no data is returned.

from wildebeest.

We would need to query D1 to detect that the instance hasn't been configured.

from wildebeest.

This code runs on every frontend request:

In this function, we can check whether the config exists (rather than just naively casting it) and throw a response.redirect() to push the user to the start-instance page instead.

from wildebeest.

And if this is problematic (from a performance point of view) we need to implement some caching of the instance data in the system somewhere (outside of D1) perhaps in a KV?

from wildebeest.