I don't really follow what you're saying
It serves static sites. I upload my files with rsync, scp, or git, and they are served
There's still a "web server" in front of those files that speaks HTTP and delivers those files. An extremely simple one, but it still exists.
What they're proposing is cutting out the "speaks HTTP" part in favor of entirely pre-recorded responses. Whether you think that's feasible or not depends on where you draw the line in the sand, but it can certainly be easier to implement than nginx.
Re:Static site hosting hurdles
by bathtub365 on Tuesday September 06, 2022 @12:33AM
(#32732872)
Web servers exist already. Does what you’re describing exist?
Re:Static site hosting hurdles
by ciprian_craciun on Tuesday September 06, 2022 @02:45AM
(#32733759)
[the author here] Well, the article does point in the last section "Putting it in practice" to my own implementation <https://github.com/volution/kawipiko>. :)
I like the idea to statically pre-generate entire HTTP responses, with all headers, and just serve a byte stream mindlessly once a URL is mapped. If TLS is handled by a separate proxy (that only does TLS termination), the "web server" becomes as trivial as it gets. Fast, simple, due to the simplicity probably bulletproof.