Hey y’all!

I am after the colelctive expertise of this fantastic community. My family and i are moving overseas for a year for a pacific adventure, which leaves my hosting setup in a bind. We will be renting out our house and i will need to move all of my ‘servers’ (read laptop and NAS) out.

All of my services are in docker.

My main services that i MUST keep are:

  • Immich
    • 600Gb or so
    • very important as we will be taking a HEAP of photos.
  • paperless
  • vaultwarden
  • custom location tracking service
  • radicale

I would also like to make it so that all of my media is still available, but i may need to get a set up at a friends house. I have jellyfin plus a bunch of *arr’s

I was thinking a mix between at a mates house and a cloud server.

any thoughts?

edit: a lot of my services are exposed publicly, via Nginx proxy manager.

  • asshole@r.nf
    link
    fedilink
    English
    arrow-up
    2
    ·
    8 months ago

    I’m not sure what the question is.

    Only thing I can think of is add a VPN like Tailscale so you don’t have to worry about any exposed services.

    • palitu@aussie.zoneOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      8 months ago

      All my hardware needs to move. And I cannot take it with me, but I want to keep my core stuff available. Looking at what people think are some good options.

      I expect it will be to a mates house with taolscale or similar in front.

  • Admiral Patrick@dubvee.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    8 months ago

    Are any of your services public facing? If so, you might want to make the VPS your reverse proxy and VPN server and have your stack at your friend’s house connect to the cloud server via VPN. The reverse proxy on the VPS would connect back over the VPN to the equipment at your friend’s house.

    This would prevent your friend from having to open ports in their router and from exposing their IP to the world (beyond their normal traffic, that is).

    Plus, it would allow you to VPN-in to manage as well as have a “kill switch” should you need it (cyberattack, etc)

    I would not run any of the *arrs on a network that is not yours (even if you have them routed through a VPN). It puts a liability on your friend and may eat up their bandwidth.

    And definitely make sure your friend knows what they’ll be hosting for you and how it may impact their network.

  • Decronym@lemmy.decronym.xyzB
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    8 months ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    CGNAT Carrier-Grade NAT
    HTTP Hypertext Transfer Protocol, the Web
    IP Internet Protocol
    NAT Network Address Translation
    SSH Secure Shell for remote terminal access
    SSL Secure Sockets Layer, for transparent encryption
    TCP Transmission Control Protocol, most often over IP
    TLS Transport Layer Security, supersedes SSL
    UDP User Datagram Protocol, for real-time communications
    VPN Virtual Private Network
    VPS Virtual Private Server (opposed to shared hosting)
    nginx Popular HTTP server

    11 acronyms in this thread; the most compressed thread commented on today has 15 acronyms.

    [Thread #491 for this sub, first seen 6th Feb 2024, 12:55] [FAQ] [Full list] [Contact] [Source code]