Does my site need HTTPS?

• docs

  1 42 10.0

  Documents about HTTPS development (by https-dev)

  

• Caddy

  403 53,904 9.5 Go

  Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS

  

This article comes off as basically victim-blaming, when it comes to "not my problem" if some bad actor injects ads etc.

The arguments against Caddy are no longer true. Caddy runs on a ton of platforms, essentially any that Go can use as compile targets (except for plan9 for the moment because of a dependency of Caddy's that has a compatibility problem https://github.com/caddyserver/caddy/issues/3615#issuecommen...). Caddy also doesn't have to run as root, nor does it with our apt/yum packages.

Also a passing comment essentially calling Let's Encrypt... with their track record at this point, I don't think that can be said.

The rest is basically just vitriol.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• dehydrated

  36 5,902 2.3 Shell

  letsencrypt/acme client implemented as a shell-script – just add water

  

> The letsencrypt auto renewer is great until you run a version of linux unsupported.

Consider using an ACME client written in shell:

* https://github.com/dehydrated-io/dehydrated

* https://github.com/acmesh-official/acme.sh

There's a minor change for the pre/post-scripts to restart your web server, and tell the web server where "/.well-known/acme-challenge/" should be served from, e.g.,:

* https://salsa.debian.org/letsencrypt-team/dehydrated/-/blob/...

But otherwise I find there are a lot fewer moving parts (and dependencies) than ACME clients written in other languages.

• acme.sh

  280 36,617 8.9 Shell

  A pure Unix shell script implementing ACME client protocol

  

> The letsencrypt auto renewer is great until you run a version of linux unsupported.

Consider using an ACME client written in shell:

* https://github.com/dehydrated-io/dehydrated

* https://github.com/acmesh-official/acme.sh

There's a minor change for the pre/post-scripts to restart your web server, and tell the web server where "/.well-known/acme-challenge/" should be served from, e.g.,:

* https://salsa.debian.org/letsencrypt-team/dehydrated/-/blob/...

But otherwise I find there are a lot fewer moving parts (and dependencies) than ACME clients written in other languages.

Suggest a related project