I propose that we offer the ability to prefix how Superstatic serves an app. For example:
If a prefix is added (it can be any valid pathname), the root directory is served only from that prefix, so "about.html" gets served at "blog/about.html"
All other configuration options including proxies etc. should apply, however they should also work as if the prefix is the root of the app. So a proxy of "/api" would be available at "/blog/api"
This will be useful for third-party developers using Superstatic as a middleware as it will let them easily mount to a prefix.
As to why it's useful for Divshot's future plans, I'll leave it to speculation. 😄
I propose that we offer the ability to prefix how Superstatic serves an app. For example:
{ "prefix":"blog" }If a prefix is added (it can be any valid pathname), the root directory is served only from that prefix, so "about.html" gets served at "blog/about.html"
All other configuration options including proxies etc. should apply, however they should also work as if the prefix is the root of the app. So a proxy of "/api" would be available at "/blog/api"
This will be useful for third-party developers using Superstatic as a middleware as it will let them easily mount to a prefix.
As to why it's useful for Divshot's future plans, I'll leave it to speculation. 😄