• 1 Post
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle



  • i worked at an animal hospital for a few years in my 20s (late 90s). I was also broke af punk kid living in a filthy punk rock house, barely able to afford my part of rent. So i’d bring home the pet food sometimes. It wasn’t really inventoried, and it’s nutrition. Do not recommend though, its a great way to get a bacterial gut infection since pet food regulations are very minimal.

    it ranges. some cat food is indistinguishable from canned tuna. the science diet I/D canine prescription tastes exactly like canned corned beef hash. the cheap stuff (kibbles&bits, fancy feast, etc) tastes exactly like you’d expect: bone meal, corn starch, and ash slag. cause thats the filler trash the cheap stuff is made of.

    generally though, most kibble just tastes like if you soaked grape nuts cereal in beef broth, and most wet food tastes about the same as canned horse. which is unpleasant.


  • The answer to your overarching question is not “common maintenance procedures”, but “change management processes”

    When things change, things can break. Immutable OSes and declarative configuration notwithstanding.

    OS and Configuration drift only actually matter if you’ve got a documented baseline. That’s what your declaratives can solve. However they don’t help when you’re tinkering in a home server and drifting your declaratives.

    I’m pretty certain every service I want to run has a docker image already, so does it matter?

    This right here is the attitude that’s going to undermine everything you’re asking. There’s nothing about containers that is inherently “safer” than running native OS packages or even building your own. Containerization is about scalability and repeatability, not availability or reliability. It’s still up to you to monitor changelogs and determine exactly what is going to break when you pull the latest docker image. That’s no different than a native package.


  • nottelling@lemmy.worldtohomeassistant@lemmy.worldLight switch advice
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 month ago

    Depends on the specific Zigbee switch, but generally yes.

    The magic is in the fact that you can decouple the relay, and use the switch as a sensor that triggers things that may or may not be related to the physical switch position.

    The other reason I like it better than a typical “smart switch” is that I can use the shellys with whatever switch I want, so I can have it match my dumb switches and use different colors.


  • shelly relays will do exactly what you want. just wire them as disconnected switches. i do this to simulate 3-way switches, but it’ll work just as well to swap circuit behavior.

    you can use a homeassistant action if you’re already using HA, or you can have the shellys call each others web api when it senses the switch.


  • nottelling@lemmy.worldtoSelfhosted@lemmy.worldConfused about Podman
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    2 months ago

    Just cause you’ve never seen them doesn’t make it not true.

    Try using quadlet and a .container file on current Debian stable. It doesn’t work. Architecture changed, quadlet is now recommended.

    Try setting device permissions in the container after updating to Debian testing. Also doesn’t work the same way. Architecture changed.

    Redhat hasn’t ruined it yet, but Ansible should provide a pretty good idea of the potential trajectory.



  • Every complaint here is PEBKAC.

    It’s a legit argument that Docker has a stable architecture while podman is still evolving, but that’s how software do. I haven’t seen anything that isn’t backward compatible, or very strongly deprecated with notice.

    Complaining about selinux in 2024? Setenforce 0, audit2allow, and get on with it.

    Docker doing that while selinux is enforcing is an actual bad thing that you don’t want.






  • I’m somewhat stuck on Unifi for wifi APs and Routers, because all the other consumer-grade devices can’t handle the number of small IoT devices I’ve got. Netgear and Asus just lose connections with ESP devices and refuse to let them connect after about a dozen. The commercial grade stuff, in addition to being too expensive, is all rack mounted, high power draw and noisy af.

    Aside from the fact that my stuff seems stable on the Ubiquiti hardware, I hate the products. The interface is terrible, Unifi insists on hiding the advanced networking behind a halfass gui, the SSH console lacks half the features of even that terrible gui, and every time i try to create a new routed network, the wifi devices stop connecting.




  • Self hosting principals aside, is this data actually important? If so, then don’t fuck around with self hosting it. Are you looking for lowest cost? Then don’t waste a bunch of money spinning your own disks.

    Amazon glacier to guarantee availability and your own encryption to guarantee privacy.

    It’s currently running me about $4/month for around 10tb that I don’t want to lose but just don’t want to deal with. An equivalent HDD solution would be around $500, that’s 10 years to break even assuming zero disk failures and zero personal maintenance time.

    Plus it’s guaranteed. Inherent multiple copies, has SLA, and there’s no worry about the service just disappearing. It’s they decide to shut down or raise prices or whatever, you can reevaluate and move.

    Edit: Glacier and similar services are meant for archival which is the term OP used. You never expect to need it again, but can’t get rid of it. Retrieval cost is mostly irrelevant, but yes much more expensive. (I’d wager still less expensive than a home RAID array.)