I write code, I write fiction, and sometimes I write rants ‧
‧ Fairy comfortable with history, esp Eur, ME. ‧
‧ Mainly interested in science fiction, history, and fantasy. ‧
‧ I self-host a lot of my software that I use everyday ‧
Tip: Telling Italians that - neither 🍅 nor ☕ is native to Italy, and they’re just butchering other peoples’ foods - enrages them. You should do it.
@philpo@feddit.org Why not do something like wireguard/tailscale in your public facing instance, having nginx there, and reroute photos.domain.com to your private server?
so, something like subdomain.domain-> dns pointed to public -> hits your public -> nginx there routes to wireguard ip of 10.1.1.5 of your private box -> <OVER WIREGUARD> -> hits your private 10.1.1.5:8080 or something?
@xtapa@discuss.tchncs.de You don’t need a “NAS” per se – just running a baremetal distro and using containers in it will suffice.
Further, while Nextcloud can work fine, I’d suggest not using it and going for individual solutions instead of something AIO – NC is fairly clunky, and fairly slow comparatively. It’s also PHP.
I personally use Proxmox + LXC/VMs in one Micro PC (i5-7xxx/24G), and Just Ubuntu with Docker compose in another(i5-6xxx/16G) alongside a couple of Oracle VMs. It works out fairly well.
For Digitizing paperwork and mail, paperless-ngx is a good solution. For your pirate ship, look into *arr solutions. jellyseerr -> sonarr/radarr -> bazarr -> jellyfin works fine.
@WhosMansIsThis@lemmy.world You Could in theory just use wireguard with nginx.
DNS pointing to Public VPS -> Nginx running on public vps -> Nginx resolving to internal wg IPS -> Any of your other devices.