• 1 Post
  • 27 Comments
Joined 2 years ago
cake
Cake day: June 26th, 2023

help-circle


  • Get a domain and set about moving over to HTTPS with Let’s encrypt and Nginx.

    Learn to write an Nginx config. NPM just works so good though.

    Fix my permission issues. I have my media zpool on 777 so all the LXCs work and I have to run Libation in a VM as root. I’ve been banging my head against this on and off for a while.

    Figure out why paperless isn’t saving to the correct place. Also, figure out where Paperless is saving to.

    Containerise Libation.

    I give friends and family access to my server via a relay, just a raspberry pi 0 with Tailscale, pihole and nginx on it. I have reasons for going this route. Anyways, get a couple more of those into the wild. Also streamline the process somewhat.

    Learn to and create an ACL config for tailscale so I can have services access nothing, users access services, and admins access everything.








  • Fairly fast, fairly simple. I arranged a friend to drive me and I was content the inconvenience fell under what I would ask of a friend. Got a local anaesthetic, the doctor and nurse talked about mundanities the entire time, which was comforting in a way. But I could see “why aren’t you focused right now” being a valid question.

    Recovery was pretty speedy, but I knew I was going to be on strong pain killers due to a surgery and timed my procedure for that.

    Lasting effects, other than sterility and slight scaring, is that pulling my balls hurts much more than it used to. The ‘suck on the balls’ move in the vids would have me doubled over, they do not want to be tugged any amount, for any reason. For a time I got a periodic sharp pain in my sack that has long since gone.

    All in all I’m happy I did it, would do it again. Would probably endure more for the benefits.

    As to the article I count in this number. Knew I didn’t want kids before my 18th and starting nagging the gp to establish a pattern. I had life changing injury at 26 due to a dangerous hobby, asked again and was referred then accepted. I don’t want kids because I’m lazy, and I will orphan them young.







  • On mobile so you’ll have to forgive format jank.

    It depends how each image handles ports if C1 has the ports set up as 1234:100 and C2 has the ports set up as 1234:500 then:

    service:

    gluetun:

    ports:

     - 1234:100 #c1
     - 1235:500 #c2
    

    […]

    Will solve the conflict

    Sometimes an image will allow you to edit it’s internal ports with an environment so

    service:

    gluetun:

    ports:

      - 1234:1000 #c1
      -1235:1234 #c2
    

    c1:

    environent:

    - UI_PORT=1000
    

    […]

    When both contsiners use the same second number, C1: 1234:80, C21235:80, and neither documents suggest how to change that port, I personally haven’t found a way to resolve that conflict.




  • My initial inception of this box was to have it request a static IP so I knew “box.ip”. Then tape then tape some thing like this:

    Box.ip Service1:port Service2:port …

    Onto the case. Then in NPM have it proxy requests to “box.ip:8096” to “tailscale.ip:8096”. But alas, I couldn’t figure it out. I could get 1 service to work but not multiple.

    I couldn’t ask someone to write the config for me, but if you’re certain it’s doable then I’ll learn to write a config. Thank you for the offer. I’m guessing for each service I tell nginx to “listen” at “port” instead of only listening to ports 80,443 and 81.

    MDNS seems like an interesting solution though, I’m going to read about that now actually, thank you for highlighting that solution to me. If I could get that working that would be ideal. I’ll have to check if the expected devices are compatible but that would make everyone’s life easier if I could just setup a cronjob on startup.


  • Thank you for the reading material, it’ll be tonight project. I think I’m just going to tell people if they want to join in the family immich/mealie/etc they’ll just have to let me into their router. They’ll get memorable addresses out of it and adblocking too. I’m pretty sure that setup is comfortably within my skill set. I thought long and hard about opening ports but the security needed is beyond me currently. Down side is cost and I’ll be managing a bunch of boxe. But I can add updating them into the monthly maintenance and if/when they come back they can be repurposed into other projects.


    I tried /locations but my service would rewrite the URL and break itself. I’d navigate to “box.ip/immich” and immich would change the address to “box.ip/login” and hang.

    I’d need to learn how to have npm lock “box.ip/immich” and let immich append “/login”. I’ll leave my test VM up and just chip away at it. I think I need the “rewrite” flag but I’m getting dangerously close to just learning how to write an nginx config instead of having npm do it for me.

    Thanks again for the pointers