lego
| letsencrypt-dns-conoha | lego | |
|---|---|---|
| 1 | 56 | |
| 13 | 7,310 | |
| - | 1.7% | |
| 0.0 | 8.9 | |
| over 2 years ago | 7 days ago | |
| Shell | Go | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
letsencrypt-dns-conoha
-
Scratch and mange the my blog
cf. k2snow/letsencrypt-dns-conoha
lego
-
Take a look at traefik, even if you don't use containers
This is one area where I've found nixos to be really helpful. I can set this up with just adding some lines to the configuration.nix (which uses [lego](https://github.com/go-acme/lego) and letsencrypt in the backend):
```nix
-
Dehydrated: Letsencrypt/acme client implemented as a shell-script
Self contained but hardly a tiny supply chain attack surface: https://github.com/go-acme/lego/blob/master/go.sum
-
Running one’s own root Certificate Authority in 2023
This ACME client looks promising, but I haven’t tried it yet: https://github.com/go-acme/lego
-
I am once again asking that "web" and "fullstack" developers...
My favorite method of obtaining certificates is with lets encrypt and LEGO
-
Where do you get/setup certificates from for your https/ssl?
Caddy where possible, and acme.sh or lego where not.
- Anyone using WireGuard with a domain name? Any ideas to lower the bills?
- Acme.sh runs arbitrary commands from a remote server
-
How do you renew SSL certificates?
Depend on host's capability... - lego - dehydrated - caddy - in case it already works as a web server, it will automatically issue and renew certs
- Automating LE renewals with dns-01?
-
LeGo CertHub v0.9.0 with Docker Support
u/gregtwallace maybe in the short term until you write your own, you could provide a hook into one of the many ACME client implementations which do DNS-01 and support the majority of major DNS provider APIs out of the box? That would make your (really great!) project much more widely usable.
What are some alternatives?
Rubel - Rubel is a cms built with Laravel and React.
letsencrypt - Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.
go-clean-architecture-web-application-boilerplate - A web application boilerplate built with go and clean architecture.
acme.sh - A pure Unix shell script implementing ACME client protocol
gobel-api - Gobel is a headless cms built with golang.
acme-dns - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
docker-based-monitoring-stack-boilerplate - This is a boilerplate for docker based monitoring stack.
autocert - [mirror] Go supplementary cryptography libraries
gobel-admin-client-example - Gobel is a headless cms built with golang.
acmetool - :lock: acmetool, an automatic certificate acquisition tool for ACME (Let's Encrypt)
terraform-ansible-openstack-boilerplate - Boilerplate for building vps using terraform and ansible.
ACL - A simple but powerful Access Control List manager