Maybe a silly question, but is simply having the thing doing the sailing running on what might be a docker container that only has access to the internet via a VPN connection okay? my friend told me this is his set up

like, logically speaking this seems to be basically fine, since the sailing ship’s data is not visible to the ISP

“retrieving” from ripping my personal DVD and BluRay collection?

are you me haha?

i assume that’s just for free podcasts?

does a wild card cert essentially mean i have use one cert which will cover all my subdomains as well as the primary domain?

Cool.

In other news, Swiss law makers claim opening and reading all mail sent to make sure it doesn’t include the phrase “monty bojangles” is “not a privacy concern”

My point is that in order to block a specific domain, you necessarily need to check it against a list of all legitimate domains being accessed

As in why is a post about VPNs on a self-hosted forum?

really? like what? i’ve been using docker completely free and unrestricted - at i think so haha

while security might be compromised if an attacker found your documentation, it could equally be compromised by having zero documentation

the easier it is for you to get things back up and running in the event of a data loss / corrupted hard drive / new machine / etc, the less likely you are to forget any crucial steps (eg setting up iptables or ufw)

supports podcasts too? what tool are you using to download those? and does ABS handle the sorting/meta data the same way it does for audio books?

maybe silly question but does tailscale tunnel operate in a similar fashion to a cloud flare tunnel? as in you can remotely access your internal service over https?

i have nginx proxy manager set up all as well, but haven’t worked out the SSL part yet, so all my internal docker services are still on http

out of interest, how did you set up https with npm?