• 1 Post
  • 14 Comments
Joined 1 year ago
cake
Cake day: August 17th, 2023

help-circle



  • Yeah, I definitely like the idea of leaving all services running locally, and connect to my VPN when needing to tinker/access.

    I do have a couple of raspberry pi’s, but I prefer to run stuff on the Nas, I only use the pi’s as clients to stream from.

    I’m gonna go lookup the difference between openvpn and wireguard :) And I have a dynamic DNS setup, that’s basically the same as a fixed IP, right?

    Thanks!


  • I definitely didn’t set up any port forwarding or routing tables when setting up the inbuilt VPN.

    Tailscale is great, and very handy to edit my compose files from, for example, work. But I didn’t think I could use it to access my services?

    I’ve become pretty familiar with docker over the years, so I’m tempted to spin up a container just to see how it works.

    I currently expose around 20 services through the reverse proxy, but only those ones that I can set a user/password for.

    I don’t mind investing the time to learn more about all this. Networking stuff has always been akin to dark magic for me, it’s time to jump in…

    Thanks!




  • Tsubodai@programming.devtoSelfhosted@lemmy.worldEBook Management
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Similar story here. Readarr (two instances, one for ebooks, another for audio). Calibre server with a watchdir to add books from libgen/elsewhere, and organising stuff. Calibre-web because trying to use calibre server on a phone is painful. WebDAV connection through phone app (Moon+) as a backup (LAN only).

    Oh, and Audiobookshelf for the audiobooks, but I generally prefer reading



  • Im probably the opposite of you! Started using docker at home after messing up my raspberry pi a few too many times trying stuff out, and not really knowing what the hell I was doing. Since moved to a proper nas, with (for me, at least) plenty of RAM.

    Love the ability to try out a new service, which is kind of self-documenting (especially if I write comments in the docker-compose file). And just get rid of it without leaving any trace if it’s not for me.

    Added portainer to be able to check on things from my phone browser, grafana for some pretty metrics and graphs, etc etc etc.

    And now at work, it’s becoming really, really useful, and I’m the only person in my (small, scientific research) team who uses containers regularly. While others are struggling to keep their fragile python environments working, I can try out new libraries, take my env to the on-prem HPC or the external cloud, and I don’t lose any time at all. Even “deployed” some little utility scripts for folks who don’t realise that they’re actually pulling my image from the internal registry when they run it. A much, much easier way of getting a little time-saving script into the hands of people who are forced to use Linux but don’t have a clue how to use it.