3 ms·
> it doesn't work with any kind of static web hosting which is a shame given that it's all static content anyways. As far as I can tell, that’s not true. The o
by realityking 5y ago
> it doesn't work with any kind of static web hosting which is a shame given that it's all static content anyways.
As far as I can tell, that’s not true. The output is completely static and just requires some very basic URL rewrites.
The Netlify config in the linked blog post (https://josephduffy.co.uk/posts/hosting-docc-archives https://josephduffy.co.uk/posts/hosting-docc-archives) illustrates this quite nicely. While Netlify has some Function-as-a-service capabilities DocC uses none of that.
- pilif 5y ago> As far as I can tell, that’s not true. The output is completely static and just requires some very basic URL rewrites. My understanding of static webpages is that there's zero processing happening server-side. "Basic URL rewrites" counts as processing in my book
- djxfade 5y agoI have hacked "URL rewriting" on Github, bu having a custom 404 page, that rewrites the URL as a query parameter. And then in the app just use the history api to take that query paramenter and replace history without an actual reload.
- tombl 5y agoI've deployed SPAs on GitHub Pages before, and you can just rename the index.html to 404.html and the site will function just as normal with no modifications.
- realityking 5y agoI think that’s an arbitrary line you’re drawing. Every webserver does some URL rewriting, otherwise you wouldn’t be able to to use /docs, /docs/ and /docs/index.html. The difference is just that this requires some more custom rewriting rules to facilitate being a single page app. I personally even disagree with that architecture, I think it’d be better to pretender the content for all pages (like, e.g., Gatsby does) but I wouldn’t call it not a static page.