Re:Setting up a static HTTPS website on your Raspberry Pi us...
by butz on Sunday October 24, 2021 @01:25PM
(#28980032)
Why even use docker for a static website server?
[ Parent
| on HN ]
Re:Setting up a static HTTPS website on your Raspberry Pi us...
by NortySpock on Sunday October 24, 2021 @01:40PM
(#28980176)
Your docker-compose file becomes configuration-as-code, and it's a one-line change to set up different websites on different ports.
Sure, I could install lighttpd myself, but docker-compose gives me a common configuration file format.
Re:Setting up a static HTTPS website on your Raspberry Pi us...
by nimbius on Sunday October 24, 2021 @01:42PM
(#28980206)
Docker is a hard dependency if you need your article on the front page of HN.
Re:Setting up a static HTTPS website on your Raspberry Pi us...
by antongribok on Sunday October 24, 2021 @01:32PM
(#28980112)
To learn a bit about Docker?
Re:Setting up a static HTTPS website on your Raspberry Pi us...
by oblak on Sunday October 24, 2021 @02:08PM
(#28980444)
Spawn a VM instead of mutilating your Pi?
Re:Setting up a static HTTPS website on your Raspberry Pi us...
by capableweb on Sunday October 24, 2021 @02:57PM
(#28980865)
Hacking is called mutilating now? Give the guy/girl a break. I don't think this is meant to be a production setup so whatever is fine, and you can always reflash it if needed so not sure I'd call this "mutilation"
Re:Setting up a static HTTPS website on your Raspberry Pi us...
by yrds96 on Sunday October 24, 2021 @01:30PM
(#28980100)
"One command" production ready server
Re:Setting up a static HTTPS website on your Raspberry Pi us...
by readingnews on Sunday October 24, 2021 @02:00PM
(#28980376)
I totally disagree with this reply, and agree with the thread starter... I really, really do not see the point of this.
One command? Did you read the github page?
At the end, this doc even has you hand editing your nginx for SSL?!? Why on earth... why not just use certbot automation? This seems totally counter to the idea. Again, am I being dense? Is this just "look what I can do with docker that makes my life more complicated"? Honestly, at this point it feels like more work for less output.
This seems way harder than installing nginx and certbot, and now I have a hard dependency on docker and whatever else you pulled in.
Re:Setting up a static HTTPS website on your Raspberry Pi us...
by marginalia_nu on Sunday October 24, 2021 @04:49PM
(#28981765)
Seems like optimizing a thing that's already pretty quick and easy to set up (and using docker and similar does not mean you don't need to understand how nginx works).
Re:Setting up a static HTTPS website on your Raspberry Pi us...
by megous on Sunday October 24, 2021 @01:56PM
(#28980329)
You mean like `apt install nginx`? :)
Re:Setting up a static HTTPS website on your Raspberry Pi us...
by codegeek on Sunday October 24, 2021 @02:10PM
(#28980467)
I am not a fan of docker for everything but 'apt install nginx' would not give you https out of the box. I am beginning to like Caddy which comes with https enabled but I have never used it in production yet.
Re:Setting up a static HTTPS website on your Raspberry Pi us...
by megous on Sunday October 24, 2021 @08:21PM
(#28983245)
If you want https you can just run certbot. It will bootstrap the nginx config. I dislike programs that change the configuration automatically, and thus run dehydrated instead of certbot, but running apt install nginx certbot and some certbot incantation to make it bootstrap your domains is not really any more bothersome, than having to figure out how docker works, and how to manage changes to my nginx config with it over time, etc..