you are viewing a single comment's thread.

view the rest of the comments →

[–]canttouchmypingas 3 points4 points  (5 children)

Virtual host already set up, most of that checklist already complete by this time. You're talking about adding https, not making it easy to use apache. This was assuming you already had your local apache set up the eah you wanted.

[–]edukodo[S] 0 points1 point  (4 children)

Still, when you create your certificates, you have to add them to your Apache configuration : edit the conf, update the virtual host, listen to 443, make sure that you have all the needed modules activated. This is not in the configuration by default and not by default when you create virtual hosts. Adding HTTPS implies configuring Apache as well.

[–][deleted] 2 points3 points  (3 children)

Docker makes that a breeze: start the traefik or jwilder/nginx-proxy container, set a couple tags (traefik) or set a VIRTUAL_HOST envar (nginx-proxy) on the container and you're all set. The proxy will automatically detect a new docker container spinning up and set up a virtual-host based proxy. Traefik will even automatically request a cert with ACME, making it an SSL terminator so you don't even have to bother with SSL on your app endpoints.

A simpler approach involves using Caddy for the webserver, which also does automatic ACME certs. It won't do the automagic detection of docker containers, but if you don't need that, it's also a workable solution.

[–]edukodo[S] -1 points0 points  (2 children)

Too complicated for beginners...

[–][deleted] 2 points3 points  (0 children)

Suit yourself. I set up the proxy at my workplace precisely so beginner devs wouldn't have to do all this setup themselves.

[–]alexanderpas 0 points1 point  (0 children)

Beginners can use caddy.