Yik Yak icon
Join communities on Yik Yak Download
Just reached my 10th service hosted with docker ๐ŸŽ‰๐ŸŽ‰
upvote 31 downvote

default user profile icon
Anonymous 1w

Docker's awesome! Now stick a reverse proxy like nginx in front so you don't have to remember dozens of port numbers

upvote 1 downvote
default user profile icon
Anonymous replying to -> #1 1w

I only use a reverse proxy for publishing 2 services to the web, I like remembering the port numbers on lan

upvote 1 downvote
default user profile icon
Anonymous replying to -> #1 1w

whats the difference between ingress and nginx, im a noob sry

upvote 5 downvote
default user profile icon
Anonymous replying to -> #2 1w

nginx proxies like npm are great for mapping a subdomain to a port number which I was saying would be great because instead of having to go to example http://192.168.1.2:12547 you can just go to https://plex.homedomain.com. Not only will nginx (NPM) shorten the work to get to a specific docker container it can use a free self-renewing SSL cert to protect traffic. But OP prefers port numbers so...

upvote 2 downvote
default user profile icon
Anonymous replying to -> #1 1w

Oh you asked about Kubernetes Ingress. Yeah, it basically performs the same function that NPM does for Docker. They both sit in front of web apps and route incoming requests. Different ecosystems but they both do TLS termination, auth, rate limiting, etc.

upvote 2 downvote
default user profile icon
Anonymous replying to -> #1 1w

Yea I prefer port numbers bc Iโ€™m not about to or donโ€™t need to publish my *arr suite to the web

upvote 1 downvote
default user profile icon
Anonymous replying to -> OP 1w

But jellyfin is the main domain p443 and jelly seer is on a sub domain p443

upvote 1 downvote
default user profile icon
Anonymous replying to -> OP 1w

If Iโ€™m away from home and want to administer thatโ€™s what WireGuard is for, and if WireGuard goes down then I have some shitty slow Ikev2 vpn on my router

upvote 6 downvote
default user profile icon
Anonymous replying to -> OP 1w

Totally agree with using WG for remote admin. But I have 93 active containers. I would just die if I had to address them all by port number...lol. So I use NPM, not to expose them to the web, but for my sanity and also it's nice to not have Chrome throw a conniption for not having proper SSL or having self-signed certs. Another thing I do is have Heimdall to organize them all into some semblance of neatness. Yeah, otherwise agree. WG is awesome for maintaining secure connectivity away from home.

upvote 1 downvote
default user profile icon
Anonymous replying to -> #1 1w

93 gah damn, Something cool I learned recently is that if I want my domain to work externally and internally I can just add a dns override in my router (I heard nat pinning may be cpu heavy on my router - not bad but I like best practices and efficiency) but the actual cool thing is that the ssl cert still works internally and doesnโ€™t throw up security errors so I can give the urls to family without ever worrying about a cert or them switching between external/internal ip. I guess if you wanted

upvote 1 downvote
default user profile icon
Anonymous replying to -> OP 1w

Similar but on internal only you can just keep port 80 open for the cert renewal

upvote 1 downvote
default user profile icon
Anonymous replying to -> OP 1w

Yeah, it's kind of an addiction. I need to go to Dockers Anonymous, lol. I started with just a handful on my Synology NAS, but Synology is a little restrictive about what ports/tools you can use so I got an old Dell server that had a good number of cores (32) and a crapload of memory (128 GB). Installed Proxmox on it, fired up a Debian VM, installed Docker and Portainer (awesome mgmt tool) and here we are 93 containers later.

upvote 6 downvote
default user profile icon
Anonymous replying to -> #1 1w

What do you have besides the basics like password mgmt, immich, media stuff, do you do a lot of like smarthome stuff, game servers, apps with a ton of microservices?

upvote 1 downvote
default user profile icon
Anonymous replying to -> OP 1w

So much hair pulling debugging containers that refused to work in certain configurations, figuring out how to proxy certain containers thru VPN, etc. You mentioned cert renewal. I try to avoid only the bare minimum ports to the big bad internet (so that's basically just WG). For cert renewal, I use LE's DNS challenge. Bonus of that method is it allows me to issue wildcard TLS certs so one cert works for all 93 containers since they have different subdomains but one root domain.

upvote 2 downvote
default user profile icon
Anonymous replying to -> OP 1w

I have an antenna on my roof that pulls in signals from nearby boats (AIS) and planes (ADSB) and transmits it to data aggregators (like FlightAware or MarineTraffic) so I have a few containers dedicated to that. A local Docker Registry and UI (like hub.docker.com but local), a local Firefox sync server, an RSS feed reader, a local speed test server (iPerf), a language translation container (LibreTranslate), a local SW Dev VC Env (Gitea - like Github but local), local music servers (Navidrome)...

upvote 4 downvote
default user profile icon
Anonymous replying to -> #1 1w

Yo thatโ€™s cool I might have to go on my roof before it gets cold

upvote 5 downvote
default user profile icon
Anonymous replying to -> OP 1w

...local iPXE server (NetbootXYZ), local docs/media (Nextcloud), local pastebin (PrivateBin), local self-monitoring tool (Uptime Kuma), automated Docker updater (Watchtower), local VS Code Server (Code Server), network monitoring system (LibreNMS), NextPVR, Prometheus, Grafana, local Unifi server, local API dev environment (Hoppscotch) and many others

upvote 3 downvote
default user profile icon
Anonymous replying to -> #1 1w

Holy shit mf knows ball

upvote 1 downvote
default user profile icon
Anonymous replying to -> #1 1w

Fellow UniFi user spotted

upvote 4 downvote
default user profile icon
Anonymous replying to -> OP 1w

Easiest way I found to get started with ADSB collection is PiAware. You can build it (using Raspberry Pi) or buy it off eBay. It comes with a RPi, a USB stick and antenna. Antenna next to your window, plug stick into RPi and your off to the races. It's good to get started because it's easy but later you can move to rooftop antennas, longer runs and moving the essential SW into a Docker container. It gives you a cool little map that shows every plane in your vicinity it can detect....

upvote 2 downvote
default user profile icon
Anonymous replying to -> #1 1w

I live a block from the beach so I think the boat stuff would be sick

upvote 6 downvote
default user profile icon
Anonymous replying to -> OP 1w

Place bets on what boat is gonna pass by, little do they know (assuming I can get range that far)

upvote 3 downvote
default user profile icon
Anonymous replying to -> OP 1w

To pickup boat traffic (AIS traffic) you'll need a similar adapter as used for planes. It's a Realtek RTL2832U. You can get it as a package from places like RTL-SDR.com, eBay or any hobby SDR (software defined radio) shop. Connect the dongle to either their dipole antenna kit or I just used an old TV antenna already on my roof (needs to be VHF), then adapters to convert it from RG6 to RG174. Then it's just a matter of configuring Docker to look for the stick and a container like ShipFeeder

upvote 5 downvote
default user profile icon
Anonymous replying to -> OP 1w

As far as range, MarineTraffic tells me I have 5 nautical miles of coverage or 338 sq. km. And AIS Catcher (the map that shows the boats) shows I can often pickup boats that are anywhere from 8-10 miles away. And that's with an antenna that's not really specifically tuned for this application (old TV antenna). With you being right at the beach and assuming you get a proper dipole antenna and good elevation, you could easily surpass that.

upvote 5 downvote