Thanks for the info, that’s definitely not how it’s working on my system, so I have something setup wrong. That explains my confusion.

I just updated my dockge container, you still have to start compose files from dockge in order to manage them. Which requires copy/pasting compose files into dockge. If you have more than 2-3 compose files, this is a pia. To me, that’s not an import of ‘existing stack’.

I used this for a bit. Can you import existing stacks yet? That was my missing feature.

I was thinking of setting this up recntly after seeing it on Jim’s garage. Do you use it for all your external services or just jellyfin? How does it compare to a fairly robust WAF like bunkerweb?

That is plan A, I have had buffering issues doing this at various hotels though. This is more of a plan b setup. That probably wasn’t clear.

How would changing dns servers change browsing habits?

That’s fair. I’m already very familiar with jellyfin, so the setup wasn’t much concern, but the other options provided are good.

I had considered that as well. I’m just thinking out loud.

I’ll be taking an android tv box with me, so the tv lockdown is a concern. I’ll be taking my laptop w me in case I need it. I considered just installing jellyfin on that too.

i understand the ‘do vacation things’, i like to watch tv while i fall asleep, so there’s that.

Some good things to think about here.

VLC is an option I hadn’t considered, I’d still have to get the media on the hdd, but something to consider for sure. I won’t be hosting any showings, this is just for personal viewing.

Yes, I’ve used it in the past to download some stuff offline for airplanes, but I think that would be more cumbersome to download that way than automate it using sonarr/radarr, (unless this has gotten better in the past year or so). I’m expecting to have quite a bit of media on the nas since it’ll be for an entire month.

Yes, mostly just to have stuff to watch without commercials.

Lol what? I’d be curious to know the amount of dns queries required for an ISP to complain about this. I’d think it would have to be massive. Also, unless it’s in their TOS, they wouldn’t really have to comply. The only downside is if they’re the only ISP for the user, which sucks and happens.

You want to to keep modification of the host to a minimum in virtualization. It makes troubleshooting so much easier.

Passwords are cached at the client for a minimum of 30 days as long as you stay logged in. this goes into specific details. (You use the bitwarden client for vaultwarden in case you weren’t aware)

Edit:clarification

Not surprising, I was hoping we’d not hit the tipping point but it’s looking grim at this point.