First, you should something decent, not DietPi. You’ve Armbian for a ready to go experience or official Debian.
Once you get into something Debian 12, you can run LXD/LXC as a containerization / virtualization solution and use the same Pi to run the official HA VM image and whatever else you would like.
Why is dietpi a worse choice? it’s still basically debian (11).
I’ve chosen DietPi because of their sane defaults that I would have to setup myself like vm swappiness, fs noatime, tmp journal, and some more I am not even aware of.
Armbian has sane defaults for SBCs as well (yes log2ram so you won’t burn SD cards) and it is way more stable and polished than DietPi with less overhead. About bare Debian, you’ve the images I linked to and you can make it log to the ram with a simple line in systemd’s config.
Storage= Controls where to store journal data. One of “volatile” (…) If “volatile”, journal log data will be stored only in memory, i.e. below the /run/log/journal hierarchy (which is created if needed).
Have had this issue myself asking with other DD card related issues.
I can’t understand why the pi foundation persist with using SD as the only physically practical storage option.
They’re looking post the point of needing a way to snap on reliable EMMC storage, as a default, in a way that doesn’t leave a cable or something permanently plugged into a USB port.
Sure, USB is a fine option, but I hate that it’s only an option and not a designed default.
Most of us only need 8GB or so for the OS, 8GB or good quality durable EMMC should hardly cost anything.
Other tiny computers and even economy notebooks and Chromebooks already use this.
As in you upgraded from a previous Lemmy? More than likely your database is migrating and it can take a while. ~30 minutes or more depending on your server.
As others have said, I’d play with routing/IP forwarding such that being VPN’d to one machine gives you access to everything — basically I would set it up as a “road warrior” VPN (but possibly split tunnel on the client [yes I know, WireGuard doesn’t have servers or clients but you know what I mean]).
Alternately, I think you could do some reverse proxy magic such that everything goes through the WireGuard box — a.lan goes to service A, b.lan to service B, etc., but if you have non-http services this may be a little more cumbersome.
Not expert, but basically you should port forward wireguard port 51820 to your server, install wireguard server, create client(s) and load QR code (or config) on android/laptop and you are set. Pi hole DNS and everything else should work just like when you are on home wifi.
You can leave your CF for public access, but do you really need PF 80 and 443 if you are using CF tunnels? (I thought you dont, but I never used CF. Feels like its more safe to hve CF tunnels if you dont need to PF, but you have a middle man you have to trust)
I would suggest having an nginx as a reverse proxy (I prefer avoiding a container as it’s easier to manage) and the have your services in whatever medium you prefer.
That was my impression as well. But since I’m on a low-RAM VPS any overhead in RAM adds up, and I wanted to know how process deduplication works before I get into it.
You would want to setup a VPN server on your linux server and vpn clients on android and laptop. I’m not knowledgeable enough to help, but you can look into wireguard
If someone really wants this service but do not want to (or cannot) host it themself, ovpn.com offer this in their client. I used to have a pi-hole selfhosted but not anymore. Using their client on my phone as well solved the problem with blocking ads while not at home.
selfhosted
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.