gravity-sync
docker-swag
gravity-sync | docker-swag | |
---|---|---|
121 | 295 | |
2,144 | 2,539 | |
- | 2.0% | |
4.4 | 9.1 | |
2 months ago | 7 days ago | |
Shell | Dockerfile | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
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.
gravity-sync
- Setting up a secondary Pi-Hole on my home network
-
Sync Local DNS and Lists on second pihole - latest way?
OR I could implement https://github.com/vmstan/gravity-sync as it's last commit was a year ago but users still seem to be using it.
- PiHole redundancy
- Have any idea ?
-
Is it possible to have 2x DHCP servers with Pi-Hole + Gravity Sync?
I run the split DHCP approach for years without issues. Having only one PiHole with DHCP Server doesn’t give you a fully redundant system. I don’t use Gravity Sync myself, but their wiki covers this case with examples: https://github.com/vmstan/gravity-sync/wiki/DHCP-Replication
- I did a dumb...
-
Two piholes and both with unbound?
the github page has a really good walkthrough and explanation
-
Running PiHole on a second server
I don't have anything add to your question. But I recommend installing gravity-sync if you're going to run two piholes. It will sync up DNS entries (among other things) automatically to the second pihole when you add a entry one of them. https://github.com/vmstan/gravity-sync
-
how much traffic would you expect to go to secondary pihole?
If you go the 2 pihole route, I strongly recommend Gravity-Synch. https://github.com/vmstan/gravity-sync
-
Using RPi for Pihole and remote access gateway
Run Pihole on both, if DNS goes down its painful. You can sync them with https://github.com/vmstan/gravity-sync
docker-swag
- Armar mi propio server
-
Guide: Setting up Local DNS WITH PORTS
I have a NAS on .0.181 and a swag container (on a different port than nginx) on .0.180 that points to my public facing services. For obvious reasons, I don't want my public domain to point to any other ports/addresses on my home network. Additionally, as elegant as swag is, it requires authentication and so won't work for simple local DNS. I now have one local domain for each server and an nginx instance on each that resolves to my different services on each.
-
SWAG + Nextcloud AIO + OnlyOffice + Openproject: Fullchain cert connections required. I have the data but I'm not sure how to plug this all together...
OP is even linking the Github... https://github.com/linuxserver/docker-swag
-
Reverse Proxied services not accessible on LAN
I have an UnRAID server with a few services (Jellyfin, Nextcloud, etc.) running on it behind Linux Servers' SWAG reverse proxy container, which is built on Nginx and Let's Encrypt. This is pointed to a DuckDNS link, which is then pointed at my domain with a CNAME. So I can access Jellyfin, for example, at jellyfin.mydomain.com. A few weeks ago, due to seemingly unrelated issues, I got a new modem/router, an Arris SURFboard G34. For the first few weeks, everything was working as before. But now, when on my LAN, I can't get to my services at the proxied domain. It times out every time. There are no errors in SWAG's logs, nothing seems amiss in the router's web interface, and the services are available both at their IP:port address and, when not on my LAN, I can access them at the domain no problem.
- Fail2Ban – Daemon to ban hosts that cause multiple authentication errors
- Mealie and Swag sut issues
- Can't get Swag instance page
- Site marked dangerous
- Reverse proxy, where to start?
-
What's the best way to connect my parent's Roku to my PC, which are on two separate networks?
Reverse proxy, probably? I use Docker SWAG, setup here, with DuckDNS and it works really well for me. There are of course many ways to reverse proxy, as I linked to earlier.
What are some alternatives?
docker-pihole-sync - A Docker Container To Sync Two Piholes
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
pihole-updatelists - Update Pi-hole's lists from remote sources easily
authentik - The authentication glue you need.
AdGuardHome - Network-wide ads & trackers blocking DNS server
traefik-examples - docker-compose configurations examples for traefik
pi-hole-keepalived
oauth2-proxy - A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.
docker-pi-hole - Pi-hole in a docker container
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
uptime-kuma - A fancy self-hosted monitoring tool
authelia - The Single Sign-On Multi-Factor portal for web apps