acmez
caddy-docker-proxy
acmez | caddy-docker-proxy | |
---|---|---|
4 | 57 | |
247 | 2,445 | |
- | - | |
6.7 | 7.4 | |
9 days ago | 6 days ago | |
Go | Go | |
Apache License 2.0 | 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.
acmez
-
Autostrada: A codebase generator for new Go projects
CertMagic uses https://github.com/mholt/acmez because lego has significant problems that made it inflexible and unreliable for use in Caddy. See the History section on that repo for an explanation.
-
Show HN: Caddy v2.5.0
Because Lego maintainers wouldn't budge when Caddy needed changes made to increase ACME reliability. Matt wrote his own implementation https://github.com/mholt/acmez and started using that in Caddy soon after. There's a deeper explanation here: https://github.com/caddyserver/certmagic/issues/71
-
Any "simple" projects with particularly well-written and/or well-documented code for a beginner to look through?
I am really proud of how elegant and well-documented ACMEz is: https://github.com/mholt/acmez
- acmez 1.0: Premier ACME client library for Go
caddy-docker-proxy
-
Take a look at traefik, even if you don't use containers
Sticky sessions are supported: https://caddyserver.com/docs/caddyfile/directives/reverse_pr..., and yes it's pluggable so you could write your own LB policy. Very easy, just copy the code from Caddy's source to write your own plugin. Let us know if you need help.
Also yes, Caddy does service discovery if you use https://github.com/lucaslorentz/caddy-docker-proxy, configuration via Docker labels. Or you can use dynamic upstreams (built-in) https://caddyserver.com/docs/caddyfile/directives/reverse_pr... to use A/AAAA or SRV DNS records to load your list of upstreams.
-
Eliminate IPv4 tax on AWS, is it that easy?
Caddy via Caddy Docker Proxy (network).
- Caddy-Docker-Proxy: Caddy as a Reverse Proxy for Docker
-
Self-Hosted Is Awesome
https://github.com/lucaslorentz/caddy-docker-proxy
It handles the routing to multiple dockerized projects on one server, by scanning docker compose files for labels and automatically setting up the required caddy configuration.
-
Keycloak SSO with Docker Compose and Nginx
My go to is always this instead:
https://github.com/lucaslorentz/caddy-docker-proxy
Single label to a docker container and with correct DNS you’ll have an automatically managed certificate right away.
-
Working on Multiple Web Projects with Docker Compose and Traefik
I have had a great experience with using this: https://github.com/lucaslorentz/caddy-docker-proxy
It combines caddy with docker-compose labels, making it super easy to spin up new projects that can immediately be exposed.
-
Caddy is the first and only web server to use HTTPS automatically and by default
If you want a slightly heavier but more robust solution, caddy-docker-proxy[0] is a plugin that listens to the Docker socket and automatically updates the Caddy configuration based on Docker labels you add to containers.
I.e. it makes Caddy act a bit more like Traefik. Most of the time, you'll just add the label `caddy.reverse_proxy={{upstreams http 8080}}` to your containers and the plugin will regenerate Caddy's configuration whenever the container is modified.
[0] https://github.com/lucaslorentz/caddy-docker-proxy
-
Nginx Development Guide
I disagree, Caddy works great in Docker. See https://caddyserver.com/docs/running#docker-compose, and CDP is a project that autoconfigures Caddy from labels https://github.com/lucaslorentz/caddy-docker-proxy. Regarding plugins, it's super simple to write a Dockerfile to add plugins, we ship a builder image variant that can be used to compile in any plugins you want.
-
How I run my servers
````
This way, Caddy will buffer the request and give 30 seconds for your new service to get online when you're deploying a new version.
Ideally, during deployment of a new version the new version should go live and healthy before caddy starts using it (and kills the old container). I've looked at https://github.com/Wowu/docker-rollout and https://github.com/lucaslorentz/caddy-docker-proxy but haven't had time to prioritize it yet.
-
Which reverse proxy are you using?
Docker labels support is available via a plugin https://github.com/lucaslorentz/caddy-docker-proxy
What are some alternatives?
boulder - An ACME-based certificate authority, written in Go.
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
caddy-json-schema - JSON schema generator for Caddy v2
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
lorelai - ✍ Generate Lorem Ipsum like a pro
traefik - The Cloud Native Application Proxy
chigo - 🌈 Lolcat in Go: Rainbows and Unicorns!
Portainer - Making Docker and Kubernetes management easy.
certmagic - Automatic HTTPS for any Go program: fully-managed TLS certificate issuance and renewal
jellyfin-media-player - Jellyfin Desktop Client based on Plex Media Player
beep - A little package that brings sound to any Go application. Suitable for playback and audio-processing.
docker-pi-hole - Pi-hole in a docker container