this post was submitted on 07 Apr 2024
493 points (96.8% liked)

linuxmemes

21263 readers
861 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     

    It's not about the destination, it's about the journey.

    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] [email protected] 31 points 7 months ago (4 children)

    Or, they could learn Ansible and get 80% of the way, and be able to reproduce the result on more than one OS. ๐Ÿฅน

    [โ€“] [email protected] 17 points 7 months ago (1 children)

    Nix is not something exclusive to NixOS, and people are already using it to make reproducible configs that work on more than one OS.

    I'm even using Ansible in what I'm currently building with Nix, because it does one thing well that I need to do: distribute files and run commands on a lot of hosts at once.

    [โ€“] [email protected] 1 points 7 months ago

    In my head they're different use cases. Nix is amazing for a living build. Ansible is more pigeon-holed to production systems where you don't want (or need) that history baked into every system

    [โ€“] [email protected] 7 points 7 months ago* (last edited 7 months ago)

    That is, until a new Ansible version breaks playbooks again, or an OS is updated in a way that messes with you playbooks, or a package is removed from the playbook but not the installed system...

    Ansible is good for ephemeral containers or VMs, but any more permanent system will eventually deviate from the set configuration.

    [โ€“] [email protected] 6 points 7 months ago (1 children)

    THIS. Or salt. You even learn something generally useful.

    [โ€“] [email protected] 1 points 7 months ago

    I use Salt BTW, but I'd be using Ansible if my previous-previous job didn't force me into Salt. ๐Ÿคญ

    [โ€“] [email protected] 1 points 7 months ago

    Getting only 80% of the way there is why it never worked before for the whole system

    Where's Ansible OS?