NGINX Unit
caddy-docker-proxy
NGINX Unit | caddy-docker-proxy | |
---|---|---|
16 | 55 | |
5,099 | 2,378 | |
0.6% | - | |
9.5 | 7.4 | |
1 day ago | 2 days ago | |
C | Go | |
Apache 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.
NGINX Unit
- Litestar – powerful, flexible, and highly performant Python ASGI framework
-
Performance benchmark of PHP runtimes
Nginx Unit application server.
- Nginx Unit: Universal Web App Server
-
Nginx Unit – Universal web app server
This is great to read! Thanks for all the great input!
I check the comments next week and make sure to address the issues / ideas mentioned. If you don’t mind feel free to drop a comment here as well with your ideas / needs. https://github.com/nginx/unit/issues/945
I will work on a compression between Nginx and Unit to close this gap in our documentation.
- Universal Web App Server
-
h5ai gallery alternative for nginx
You could try running h5ai with NGINX UNIT.
-
Which reverse proxy are you using?
nginx, but nginx-unit looks very interesting. I might switch a few docker containers to use it before trying to use it natively.
- Universal Web App Server – Nginx Unit
-
Nginx front / Nginx Unit-PHP Back
unix:/filesocketheadache (problems) verses unix:@abstractsocketmagic (problem solved)
-
Easy to use docker-container for your applications
Try Nginx Unit to get away from the php-fpm complexity. It runs on http by default so it's super easy to spin up and access by itself (no need for an extra http server) or behind another http gateway as a simple proxy.
caddy-docker-proxy
-
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
-
My repository of the week: NGINX Proxy - Automated nginx for your containers
Or caddy-docker-proxy: https://github.com/lucaslorentz/caddy-docker-proxy
What are some alternatives?
uvicorn - An ASGI web server, for Python. 🦄
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
traefik - The Cloud Native Application Proxy
Traefik-v2-examples - Traefik v2 guide by examples
Portainer - Making Docker and Kubernetes management easy.
filemanager - 📂 Web File Browser
jellyfin-media-player - Jellyfin Desktop Client based on Plex Media Player
snunit - Scala Native HTTP server based on NGINX Unit
docker-pi-hole - Pi-hole in a docker container