@[email protected] 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.
Abe
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.
- 0 Posts
- 6 Comments
Joined 1 year ago
Cake day: October 21st, 2024
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
@[email protected] 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:8080or something?
@[email protected] 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.
352·11 months ago@[email protected] There is absolutely no way any starter will see that page and not be intimidated. I am a well seasoned selfhoster and even I saw that and went “Wow that’s a lotta words and images on a single page.”
Even arch wiki has sensible ToC with pages divided into what the current topic is.
@[email protected] Fwiw, LinuxServer still maintains a resilio-sync docker image for 3.0.0. They are fairly trustworthy.
https://hub.docker.com/r/linuxserver/resilio-sync
@[email protected] You could use Frigate for the ‘feature’ set, no? frigate+HA should work very well for the use case. Rest you should be okay with something that does RTSP and feeding that to frigate/HA, no? I remember researching something about this last year, and found that Reolink IIRC offers that.