• 2 Posts
  • 17 Comments
Joined 9 months ago
cake
Cake day: March 26th, 2024

help-circle
  • OpenScale works great and kind of does what you want. If you have an old Android phone laying around you can have it persistently connected to a cheap Bluetooth scale. Functional, but at a much have higher power cost than an ESP32 solution. Automated database exports to a local file (on the android device) and Syncthing can move your data around for analysis.

    The good folks over at Gadgetbridge might have a solution too, although their list of supported scales looks pretty short.

    You might also look into making a project like rmfakecloud to trick your Fitbit device into pushing data to a local server.

    Not sure about home assistant though, I’ve never used it.




  • sunstoned@lemmus.orgtoMemes@lemmy.mlWish me luck at this critical milestone
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    edit-2
    4 months ago

    I’m a big fan of buying power tools twice. I happen to go Ryobi for the first round but Harbor Freight / Northern Tool are probably similar.

    If you can stand the fuss, buy corded tools and skip the brand loyalty that comes with batteries.

    The biggest killer of cheaper power tools is generally heat. There are plastic components in the drive train. They hold up great to short jobs, but heat is their kryptonite. If you let a Ryobi tool cool down whenever you notice it getting warm to the touch it’ll last a long time. If you need to run a tool for hours at a time then skip the fuss and go straight to a more brand with a good reputation like DeWalt, Makita, Bosch, or Milwaukee.






  • Is there a reason you’re not considering running this in a VM?

    I could see a case where you go for a native install on a virtual machine, attach a virtual disk to isolate your library from the rest of the filesystem, and then move that around (or just straight up mount that directory in the container) as needed.

    That way you can back up your library separately from your JF server implementation and go hog wild.


  • Syntax-wise, it’s meant to be identical. I got on board when they were the only ones that enabled rootless (without admin privileges) mode. That’s no longer the case since rootless docker has been out for a while.

    I’m personally a fan of the red hat docs and how-to’s on podman over the mixed bag of tech bro medium articles I associate with docker.

    At the end of the day this is a bit of a Pokemon starter question. If your top priority is to get a reasonably common and straightforward job done just pick one and see where it takes you! :)



  • My solution is to use Rathole. I rent a wildly cheap (2 core, 4GB memory) VPS and basically just run Traefik there. Then I use Rathole to make some services hosted on my desktop available to Traefik.

    I like this solution better than Wireguard for my application. It reduces attack surface to services you’ve explicitly set up, rather than a full data layer trunk between your machine and a potential malicious actor.





  • I’m an old man when it comes to major changes. If it’s salvageable then maybe stick with what you’ve got. Have you used lazy docker or watchtower?

    Lazy docker should give you a more reliable interface (TUI, over ssh, not a GUI)

    Watchtower (aims to) update your containers for you so you don’t have to go through this pain in the first place :)

    Personally, I run my Nextcloud and Jellyfin servers on NixOS with auto updates on. It’s been chugging along great!