|
|
|
|
|
|
by lipanski
813 days ago
|
|
|
If this is the nano version then let me share the pico alternatives with you: * BusyBox httpd [1] * thttpd [2] * Lwan Web Server [3] * gatling [4] I built and maintain a super tiny Docker image (~158KB) for serving static files [5]. My current implementation is based on Busybox httpd and scratch but I also tried out thttpd in the past, which worked well but came with a high memory footprint in some cases. thttpd was used to serve big projects back in the day but it doesn't seem maintained any more. The other two projects were on my list of things to try out. All these projects should compile to binaries <500KB. By comparison nano-web builds a 18.5MB image on my machine. In my experience you can't go below 5-6MB with Alpine (scratch is the way to go if you can compile statically) and you can't go below ~500KB with Golang or Rust, at least not for serving http requests (C or ASM is probably the way to go). Note that I'm not saying that small is always better, it probably depends on your use case and there are reasons for using nginx for a static website as well. [1] https://www.busybox.net/
[2] https://www.acme.com/software/thttpd/
[3] https://lwan.ws/
[4] https://www.fefe.de/gatling/
[5] https://github.com/lipanski/docker-static-website |
|
|
> you can inject configuration variables into it at runtime and access them from within your frontend code
Is there a way to do that with BusyBox httpd or the others?