By the way, is there a really minimal, really fast, reasonably secure, zero-cofig single-binary web server which would only support HTTP GET and just expose all the static content in a given directory over it?
Show HN: Nano-web – a low latency one binary webserver designed for serving SPAs
11–20 of 119 posts
Re: Show HN: Nano-web – a low latency one binary webserver designed for serving SPAs
#12Can you elaborate "CloudFront doesn't support index pages in subdirectories" and how does it not work? I'm not much into them these days but if I remember correctly in the 4-5 years prior, they just works! In-fact, CloudFront was easier to serve static web assets than serving directly from S3. Or have I misunderstood what you meant?
Re: Show HN: Nano-web – a low latency one binary webserver designed for serving SPAs
#13Can you elaborate "CloudFront doesn't support index pages in subdirectories" and how does it not work? I'm not much into them these days but if I remember correctly in the 4-5 years prior, they just works! In-fact, CloudFront was easier to serve static web assets than serving directly from S3. Or have I misunderstood what you meant?
Re: Show HN: Nano-web – a low latency one binary webserver designed for serving SPAs
#14By the way, is there a really minimal, really fast, reasonably secure, zero-cofig single-binary web server which would only support HTTP GET and just expose all the static content in a given directory over it?
Re: Show HN: Nano-web – a low latency one binary webserver designed for serving SPAs
#15By the way, is there a really minimal, really fast, reasonably secure, zero-cofig single-binary web server which would only support HTTP GET and just expose all the static content in a given directory over it?
readme: http://canonical.org/~kragen/sw/dev3/httpdito-readme
source (single file): http://canonical.org/~kragen/sw/dev3/server.s
it might be reasonable to configure its port and mime types map on the command line instead of in the source, but at the moment it's arguably a bit too zero-configuration
it runs on linux, can handle about 20000 hits per second, has about 20 kilobytes of memory footprint when idle, and needs another 4 kilobytes per concurrently open connection (though the kernel needs several times that)
20000 hits per second is not really fast in the sense that other servers on the same hardware and kernel can handle more than twice that, but it can saturate a gigabit pipe if your files average 7 kilobytes or more
Re: Show HN: Nano-web – a low latency one binary webserver designed for serving SPAs
#16Can you elaborate "CloudFront doesn't support index pages in subdirectories" and how does it not work? I'm not much into them these days but if I remember correctly in the 4-5 years prior, they just works! In-fact, CloudFront was easier to serve static web assets than serving directly from S3. Or have I misunderstood what you meant?
Re: Show HN: Nano-web – a low latency one binary webserver designed for serving SPAs
#17https://github.com/varbhat/serv
* Serve the SPA (fallback to index.html): `serv -spa`
* Serve the directory and all it's contents: : `serv -dir=/path/to/my/dir`
Re: Show HN: Nano-web – a low latency one binary webserver designed for serving SPAs
#18By the way, is there a really minimal, really fast, reasonably secure, zero-cofig single-binary web server which would only support HTTP GET and just expose all the static content in a given directory over it?
Re: Show HN: Nano-web – a low latency one binary webserver designed for serving SPAs
#19https://github.com/radiosilence/nano-web?tab=readme-ov-file#...
Re: Show HN: Nano-web – a low latency one binary webserver designed for serving SPAs
#20By the way, is there a really minimal, really fast, reasonably secure, zero-cofig single-binary web server which would only support HTTP GET and just expose all the static content in a given directory over it?