caddy-docker-proxy
node-red-contrib-home-assistant-websocket
Our great sponsors
caddy-docker-proxy | node-red-contrib-home-assistant-websocket | |
---|---|---|
54 | 4 | |
2,358 | 466 | |
- | - | |
7.4 | 9.6 | |
3 days ago | 4 days ago | |
Go | TypeScript | |
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.
caddy-docker-proxy
- 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
-
Caddy Repository from Lucas lorentz cant use Caddyfile?
I am trying now for some Days to use a Caddyfile additionaly to the auto generated files from lucas lorentzes caddy repositroy. https://github.com/lucaslorentz/caddy-docker-proxy
node-red-contrib-home-assistant-websocket
-
Is there any good tutorial on custom nodes?
It's tricky. What I did was start from the https://github.com/zachowj/node-red-contrib-home-assistant-websocket project, and cleared that out completely.
-
Node-Red alternatives
It's actually not that hard, there are some caveats, but there are a couple of very good examples for a dev/build environment, the homeassistent websocket module's build system was pretty easy to reuse.
-
Is this the ultimate self-hosting setup? I think so...
Home Assistant Websocket Plugin for Node Red - Use Node Red for Home Assistant automation
-
How can I control an entity with Node-RED with a domain that it doesn't suggest?
Might be a bug with the NR websocket contrib. You could log an issue here and see what comes of it. Or maybe it's an HA bug.
What are some alternatives?
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
homeassistant-desktop - 🎛 Desktop application (Windows / macOS / Linux) for Home Assistant built with Electron
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
docker-pi-hole - Pi-hole in a docker container
traefik - The Cloud Native Application Proxy
docker-cloudflared - Cloudflared proxy-dns Docker image
Portainer - Making Docker and Kubernetes management easy.
docker - ⛴ Docker image of Nextcloud
jellyfin-media-player - Jellyfin Desktop Client based on Plex Media Player
docker-mysql-cron-backup - Docker image to backup all your databases periodically
kubernetes - Production-Grade Container Scheduling and Management