Comment on Is ansible worth learning to automate setting up servers?

• fine_sandy_bottom@discuss.tchncs.de ⁨6⁩ ⁨months⁩ ago

  I guess it depends what you’re in to but it doesn’t make much sense for me.

  Most everything I do on servers now is in docker containers, and I back up the compose files and data from those so they can be deployed to a new server pretty easily.

  Migrating between servers only happens once every several years. I feel like managing an ansible config would just be an additional layer of complexity rather than making it easier. Their isn’t much configuration outside of docker in my case anyway.

  source

  • crony@lemmy.cronyakatsuki.xyz ⁨6⁩ ⁨months⁩ ago

    I tend to grow my feel of server every couple months, and that requires me to once again setup everything for the beginning, settings, sshd, update debian if old version, new user for ssh, docker/podman, …

    Quite literally added new vps to my fleet and spent 4 hourson setting all that up, when it could have been a simple ansible script.

    source

    • oldfart@lemm.ee ⁨6⁩ ⁨months⁩ ago

      Then yes, learning Ansible is a good way to have base OS settings for your systems. I love that it’s agentless - works over SSH.

      The ugly part is that they keep updating it in a backwards incompatible way. In one version the paramerer is called “file” and in another it’s “dest”, they pull shit like this and don’t provide a tool to update playbooks automatically.

      But updating is rather optional.

      source

      • crony@lemmy.cronyakatsuki.xyz ⁨6⁩ ⁨months⁩ ago

        Sed comes into play there, or :%s in vim, whichever you prefer ;)

        source