5 ms·

I guess everyone has their own solution to this. Here's mine: - Write some static html and one stylesheet - Pay DigitalOcean for the cheap plan - Run nginx

I guess everyone has their own solution to this. Here's mine: - Write some static html and one stylesheet - Pay DigitalOcean for the cheap plan - Run nginx + letsencrypt - Apply linux security updates promptly - Occasionally pay to renew the domain So yeah, that does take a little bit of (very simple) systems administration skills, and it's a recurring commitment. But there is no such thing as a successful but unmaintained web site. Even if you don't have to maintain the infrastructure, you have to maintain the content. So I don't mind the occasional maintenance tasks. They keep me in touch with linux systems administration in a good way. It's cool to write your own web server software, I guess. But serving static html is pretty much a solved problem. I felt like the OP was inventing problems with it that don't really exist in practice.

bitexploder 4y ago
Let the updates run automatically. Put certbot on a cron. Ride it until ubuntu LTS I am on dies. So easy. :)
- doodlesdev 4y ago
  You can also use Caddy in place of NGINX and let it handle Lets Encrypt for you :)
  - bitexploder 4y ago
    I hadn’t really touched caddy in a while. For a static site I may just do that if my cron script ever falls over. I was also feeling hipster and wanted to play with Justine’s redbean. It is sort of appealing to just drop a binary off somewhere and be done with it, but like `apt install nginx` is also trivial as a user :)
coder543 4y ago
I used to do something similar, but DigitalOcean App Platform's $0/month "starter" plan[0] hosts a static site for even less effort. When I was self-hosting on a DigitalOcean droplet, I was using Caddy instead of nginx, which handled letsencrypt for me, so that was nice. [0]: https://www.digitalocean.com/pricing/app-platform https://www.digitalocean.com/pricing/app-platform
- justsomehnguy 4y ago
  I'm using Caddy with Docker labels auto-configuration. It's somewhat PITA to configure if you don't need a public cert, eg something for testing or not having a public A/AAAA record, but otherwise the automagik just works. The only negative moment is what Caddy container restarts when the dependent containers starts|restarts, so you briefly lose all connectivity to all sites behind Caddy. [0] https://github.com/lucaslorentz/caddy-docker-proxy https://github.com/lucaslorentz/caddy-docker-proxy
  - jacooper 4y ago
    There are also security implications that the webserver has access to the socket directly.
    - justsomehnguy 4y ago
      > Each caddy docker proxy instance can be executed in one of the following modes. > Server > Acts as a proxy to your Docker resources. The server starts without any configuration, and will not serve anything until it is configured by a "controller". > Server instances doesn't need access to Docker host socket and you can run it in manager or worker nodes. This can be mitigated by running in the Controller mode

bitexploder 4y ago

Let the updates run automatically. Put certbot on a cron. Ride it until ubuntu LTS I am on dies. So easy. :)

doodlesdev 4y ago
You can also use Caddy in place of NGINX and let it handle Lets Encrypt for you :)
- bitexploder 4y ago
  I hadn’t really touched caddy in a while. For a static site I may just do that if my cron script ever falls over. I was also feeling hipster and wanted to play with Justine’s redbean. It is sort of appealing to just drop a binary off somewhere and be done with it, but like `apt install nginx` is also trivial as a user :)

coder543 4y ago

I used to do something similar, but DigitalOcean App Platform's $0/month "starter" plan[0] hosts a static site for even less effort. When I was self-hosting on a DigitalOcean droplet, I was using Caddy instead of nginx, which handled letsencrypt for me, so that was nice. [0]: https://www.digitalocean.com/pricing/app-platform https://www.digitalocean.com/pricing/app-platform

justsomehnguy 4y ago
I'm using Caddy with Docker labels auto-configuration. It's somewhat PITA to configure if you don't need a public cert, eg something for testing or not having a public A/AAAA record, but otherwise the automagik just works. The only negative moment is what Caddy container restarts when the dependent containers starts|restarts, so you briefly lose all connectivity to all sites behind Caddy. [0] https://github.com/lucaslorentz/caddy-docker-proxy https://github.com/lucaslorentz/caddy-docker-proxy
- jacooper 4y ago
  There are also security implications that the webserver has access to the socket directly.
  - justsomehnguy 4y ago
    > Each caddy docker proxy instance can be executed in one of the following modes. > Server > Acts as a proxy to your Docker resources. The server starts without any configuration, and will not serve anything until it is configured by a "controller". > Server instances doesn't need access to Docker host socket and you can run it in manager or worker nodes. This can be mitigated by running in the Controller mode