• 3 Posts
  • 91 Comments
Joined 2 years ago
cake
Cake day: June 17th, 2023

help-circle


  • Depends. You could argue that economically speaking it’s not worthwhile to stop and cite people for speeding. Police do have discretion on that kind of thing so not the best example, but still, there’s probably stuff that isn’t good for the bottom line that just needs to happen. The government is not a business.

    Now when I say “depends”, I would be more inclined to go after a small number of people committing massive fraud than a large number committing minor acts of fraud. In the first case I think charges would discourage future abuse but in the second probably not. It wouldn’t be a vast, organized network of people doing the same thing, but a bunch of people that happened to notice the same opportunity. I think you’d do just as well having applicants read and sign a paper that goes over the penalties of abuse (while spending very little resources on enforcement).



  • The struggle with KeePass conflicts is real. Put basically the problem occurs when you change a DB on device A, change the same DB on device B, and then you sync them using Syncthing. That might happen for me once a month.

    I think I found a process that can reduce the occurrence of conflicts, mostly, not entirely. Instead of one DB that every device shares I have one DB per device (i.e. the KeePass file includes the name of the device). Most of the time this can’t possibly cause a conflict because device A only saves to its own DB. The only time it could create a conflict is if I need to pull in an entry that I made on another device. That’s a manual process for me and it makes me more aware that a conflict could happen. I make sure the device I’m syncing from is active in Syncthing, and if it is there’s almost no chance of a conflict.

    A one-way sync option for KeePass would make conflicts almost impossible so I think I’ll propose that or work on a plugin for it.






  • I don’t think it necessarily needs to be either or. Organizing the playbooks and folders myself can be stressful so an extra layer of organization might work best for you. There are other tools like Semaphore that are specifically built for Ansible executions though. Might need a lot of duct tape for Jenkins to run Ansible.

    And if you’re not a fan of yaml you can always nope out and embed shell scripts into your Playbooks. You can even put Docker compose yaml inside a playbook but it’s a bit inception-y and I don’t really recommend that.









  • Programming is generally not needed when self-hosting. At best you might learn Ansible, Puppet, Salt, or Terraform, but that’s for advanced scenarios (e.g. easily shifting the workloads between machines or into the cloud).

    Learning the ins-and-outs of containers will get you the biggest return on investment. They’re not strictly necessary but most tools will expect that is the common use-case and the community won’t be as much help. Until you know more about containers I would also recommend Docker over Podman. It has a few more “conveniences” than Podman and orgs like LinuxServer will target Docker as the engine.