home.social

Search

1000 results for “ansible”

  1. Leistungsnachweis / Benotung von Studis durchautomatisieren?

    Via #ansible #configurationdrift bei 30 #iaas -Instanzen transparent machen...why not?

    Mein credo wird immer sein: alles weg automatisieren, am liebsten mich selbst

  2. Automation and configuration management are not just for comfort. The gains are security, auditability and operational freedom.

    #ansible #role #gitea #nginx #postgresql #iac #devops

    tomsitcafe.com/2026/02/27/gite

  3. Ansible and YunoHost are kind of an iffy combination.

    YunoHost is based on a "continuous integration" model. So each time you run it, it tries to get the most up-to-date versions of the software. Sometimes this fixes problems, but other times, things break. There isn't a clean "release" or "version" schedule to stick to.

    Which is in conflict with the notion of "repeatable installation" that motivated using a configuration management system like Ansible. Which is really closer to what I feel like I need as a DIY-maintainer.

    The continuous-integration approach requires a larger risk of unpredictable demand for IT work. Any upgrade can result in breakage that is hard to recover from.

    YunoHost provides a through-the-web GUI approach to managing the configuration, which eases the ongoing burden of the work, but it obviously can't eliminate it -- and apps will occasionally break.

    And for my needs, YunoHost doesn't cover all the configuration: I still need to get in and make changes to configuration files. Ansible is handy for doing that in a predictable way -- so long as the configuration files don't change much.

    I'm not sure there's a solution for this, other than acknowledging that IT work is an ongoing project expense: either in my time, or in money, if I were to pay someone else to do it.
    #FilmFreedom #VirtualStudio #Infrastructure #Ansible #YunoHost

  4. Ansible and YunoHost are kind of an iffy combination.

    YunoHost is based on a "continuous integration" model. So each time you run it, it tries to get the most up-to-date versions of the software. Sometimes this fixes problems, but other times, things break. There isn't a clean "release" or "version" schedule to stick to.

    Which is in conflict with the notion of "repeatable installation" that motivated using a configuration management system like Ansible. Which is really closer to what I feel like I need as a DIY-maintainer.

    The continuous-integration approach requires a larger risk of unpredictable demand for IT work. Any upgrade can result in breakage that is hard to recover from.

    YunoHost provides a through-the-web GUI approach to managing the configuration, which eases the ongoing burden of the work, but it obviously can't eliminate it -- and apps will occasionally break.

    And for my needs, YunoHost doesn't cover all the configuration: I still need to get in and make changes to configuration files. Ansible is handy for doing that in a predictable way -- so long as the configuration files don't change much.

    I'm not sure there's a solution for this, other than acknowledging that IT work is an ongoing project expense: either in my time, or in money, if I were to pay someone else to do it.
    #FilmFreedom #VirtualStudio #Infrastructure #Ansible #YunoHost

  5. Ansible and YunoHost are kind of an iffy combination.

    YunoHost is based on a "continuous integration" model. So each time you run it, it tries to get the most up-to-date versions of the software. Sometimes this fixes problems, but other times, things break. There isn't a clean "release" or "version" schedule to stick to.

    Which is in conflict with the notion of "repeatable installation" that motivated using a configuration management system like Ansible. Which is really closer to what I feel like I need as a DIY-maintainer.

    The continuous-integration approach requires a larger risk of unpredictable demand for IT work. Any upgrade can result in breakage that is hard to recover from.

    YunoHost provides a through-the-web GUI approach to managing the configuration, which eases the ongoing burden of the work, but it obviously can't eliminate it -- and apps will occasionally break.

    And for my needs, YunoHost doesn't cover all the configuration: I still need to get in and make changes to configuration files. Ansible is handy for doing that in a predictable way -- so long as the configuration files don't change much.

    I'm not sure there's a solution for this, other than acknowledging that IT work is an ongoing project expense: either in my time, or in money, if I were to pay someone else to do it.
    #FilmFreedom #VirtualStudio #Infrastructure #Ansible #YunoHost

  6. Ansible and YunoHost are kind of an iffy combination.

    YunoHost is based on a "continuous integration" model. So each time you run it, it tries to get the most up-to-date versions of the software. Sometimes this fixes problems, but other times, things break. There isn't a clean "release" or "version" schedule to stick to.

    Which is in conflict with the notion of "repeatable installation" that motivated using a configuration management system like Ansible. Which is really closer to what I feel like I need as a DIY-maintainer.

    The continuous-integration approach requires a larger risk of unpredictable demand for IT work. Any upgrade can result in breakage that is hard to recover from.

    YunoHost provides a through-the-web GUI approach to managing the configuration, which eases the ongoing burden of the work, but it obviously can't eliminate it -- and apps will occasionally break.

    And for my needs, YunoHost doesn't cover all the configuration: I still need to get in and make changes to configuration files. Ansible is handy for doing that in a predictable way -- so long as the configuration files don't change much.

    I'm not sure there's a solution for this, other than acknowledging that IT work is an ongoing project expense: either in my time, or in money, if I were to pay someone else to do it.
    #FilmFreedom #VirtualStudio #Infrastructure #Ansible #YunoHost

  7. Mám tady základ role pro ansible github.com/Vitexus/mastodon_se a uvítal bych spolupráci.

    Cílem je, aby to umělo mastodon server nainstalovat, zkonfigurovat a zakutalizovat.

    #ansible #Mastodon #Automatizace

  8. Fully automated the patching of my linux servers with #Ansible using a workflow. The Job runs scheduled every day:

    - Publishing a new Content-View version on Satellite and promoting it
    - Patching all inventory hosts to the latest state
    - Rebooting systems, if necessary

    Ansible Playbook to patch systems:

    - name: Patch all systems and reboot if required
    hosts: "{{ host }}"
    gather_facts: true
    become: true

    tasks:
    - name: Ensure all updates are applied
    ansible.builtin.package:
    update_cache: true
    name: "*"
    state: latest
    update_only: true

    - name: Check to see if update is required
    ansible.builtin.command: dnf needs-restarting -r
    register: result
    changed_when: false
    failed_when: result.rc not in [0, 1]
    ignore_errors: true

    - name: Reboot server if needed
    ansible.builtin.reboot:
    when: result.rc | int == 1

    #linux #maintanance #patch #ansible #rhel #sysadmin #homelab

  9. Today will be fun. I'll define a colorscheme and set up configs for kitty, hyprland, waybar, neovim, tmux and fish for my #ansible #playbook. Basically the whole #tilingwindowmanager setup, but reproducible. Also thinking about trying #arch again. Could automate the entire installation and configuration using ansible.

    #automation #dotfiles #customization #linux

  10. @aaronmamparo I have an #ansible playbook that manages my nodes. It's not 100% perfect but it does all the things I need to keep them running smoothly. The #Kubernetes stuff I leave unautomated for educational purposes (where I will experiment with #Helm, #Carvel tooling, etc).

  11. Today I wrote an #Ansible module that knows how to parse and update #CUPS configuration files because I needed one and couldn't find one already written by somebody else. Share and enjoy!
    #Linux #FOSS #OpenPrinting #ConfigurationAsCode
    blog.kamens.us/2024/12/28/foss

  12. Today I wrote an #Ansible module that knows how to parse and update #CUPS configuration files because I needed one and couldn't find one already written by somebody else. Share and enjoy!
    #Linux #FOSS #OpenPrinting #ConfigurationAsCode
    blog.kamens.us/2024/12/28/foss

  13. Today I wrote an #Ansible module that knows how to parse and update #CUPS configuration files because I needed one and couldn't find one already written by somebody else. Share and enjoy!
    #Linux #FOSS #OpenPrinting #ConfigurationAsCode
    blog.kamens.us/2024/12/28/foss

  14. Today I wrote an #Ansible module that knows how to parse and update #CUPS configuration files because I needed one and couldn't find one already written by somebody else. Share and enjoy!
    #Linux #FOSS #OpenPrinting #ConfigurationAsCode
    blog.kamens.us/2024/12/28/foss

  15. The ProLUG Big Book of Labs by Scott Champine is free with a Leanpub Reader membership! Or you can buy it for $20.00! leanpub.com/theprolugbigbookof #SystemsEngineering #Ansible

  16. The ProLUG Big Book of Labs by Scott Champine is free with a Leanpub Reader membership! Or you can buy it for $20.00! leanpub.com/theprolugbigbookof #SystemsEngineering #Ansible

  17. The ProLUG Big Book of Labs by Scott Champine is free with a Leanpub Reader membership! Or you can buy it for $20.00! leanpub.com/theprolugbigbookof #SystemsEngineering #Ansible

  18. The ProLUG Big Book of Labs by Scott Champine is free with a Leanpub Reader membership! Or you can buy it for $20.00! leanpub.com/theprolugbigbookof #SystemsEngineering #Ansible