AGH with upstream lookups over DoH, and adblock list from oisd.nl.

Split-brain topology to give internal IP in preference to public IPs for my selfhosted services, and selective routing of a defined set of domains to a geo-unblocking service so I can access things like BBC iplayer etc. from my home network.

I suspect your friends probably don’t need access to your whole media stack.

What parts they do need access to, and from what type of devices, will determine the best approach.

At least on Linux you just include the bind address and port on the cmdline, e.g:

./filebrowser -a 127.0.0.1 -p 8008

EDIT: Just downloaded the Windows bin and seems to be exactly the same.

Seeing as you say port 25565 you’re using Minecraft Java, so i’d prob just do this:

https://blogs.oracle.com/developers/post/how-to-set-up-and-run-a-really-powerful-free-minecraft-server-in-the-cloud

Couple of points:

1. Make your account PAYG to lessen likelihood of server being shutdown (will still be free)

2. Take nightly backups just in case.

You could stump up for a management console like AMP if you want to make things a bit easier.

GL.

Gaming server? VPN? File-sharing?

I don’t self host anything where it would impact me unduly if it went down while I was on holiday to the point where I’d have to break state and fix stuff.

A password manager falls in that camp so it’s paid-for Bitwarden every night every day every possible way for me.

Sure Vaultwarden suits others - generally those who either want control of their data, smaller target on their back than a public instance user, watching their pennies etc.

Normally fine but if you want to be more careful about what is being pushed to your server you can use something like diun to get notifications and run updates manually.

Personally I love dockcheck, which I think is by a guy on the sub. I tend to just run that every now and again and be done with it unless I am notified of a perssing update, although I do still have a couple of things I don’t care too much about just auto update with watchtower.

You can either point the first proxy to the second proxy, or point it to the backends directly. Depends if you have firewalls in the way that stop the VPS proxy reaching your backends directly; or if that internal nginx instance is dong anything clever like handling auth, adding headers etc. etc.

In your instance I’d more likely have the VPS locked down and unable to access my internal resources and just open up its access to my internal nginx instance. Therefore chaining proxies would be my approach but there’s no right or wrong.

I’d go for an ESP8266/ESP32 with a telegram bot and LED (based sign) hanging off it. Just send a msg on telegram to turn it on/off.

That having been said loads of ways to trigger the sign status - it could poll a website to see what status it should display and you have a mechanism of updating that status yadda yadda yadda.

Note that those little chips needs wifi so you’d need to be able to connect it to wifi and have it get public internet access (or whatever you decide to control it). Loads of posts/youtube exist about driving WS2812 LEDs, or making your own DIY LED ‘neon’ signs. Cool little projects.