Today I spend several hours watching #ansible playbooks deploying a system - iteratively fixing issues. It takes ages, even when using --start-at-task. And in the end it can't be reproduced in just a few days due to downloaded lxc-containers.

I'd really, really like to use #guix deploy instead, which builds the config-files and pops up a new system - instead of execution command after command. Anyhow I eagerly missing some handling for secrets like #debops provides.

Any ideas?

Ich bin ein Freund von #debops, einer großen Sammlung aufeinander abgestimmter #Ansible roles für Debian. Damit umgehe ich zumindest den letzten Punkt.
@txt_file

The documentation page about the playbooks in #DebOps also needs to be rewritten, so I'll use this excuse to expand it a bit and document how the playbooks can be used within the project and with greater #Ansible ecosystem.

I'm currently working on reorganizing #Ansible playbooks in #DebOps a bit to remove a large set of #symlinks in the repository. The different service playbooks will be grouped into "layers" which then will be included in the "site.yml" playbook.

https://github.com/debops/debops/tree/master/ansible/playbooks

I just realized that my nephew was born a few days before I started working on a project that eventually became @debops, about 9 years ago. It's a weird thought, working on a software project and having an actual human being as a comparsion for that project's age.

#DebOps #Ansible

@kirschwipfel Thanks and hello again! 🙂 I might add #Mastodon support into #DebOps in the future, install looks easy enough.

Hello, Fediverse!

It's #introduction time. I'm 40ish geek from #Poznań, #Poland. I'm #bilingual, pretty good #English and native #Polish. I like #scifi, #space and #futurism in media, good #books, #chess and games, currently on #NintendoSwitch. I'm #asexual, most likely #aromantic and an #introvert at heart.

I'm employed as a #Linux #sysadmin. I created #DebOps, a set of #Ansible playbooks and roles which manage #Debian and #Ubuntu hosts and data centers. I use #FOSS software daily since 2001.

@alceawisteria @koyu
As for software, i prefer to use #ansible and #debops to manage machines. But for something docker-based i think @coopcloud are doing wonderful work.
Also, for more of a personal and home use case, @freedomboxfndn

@teleclimber
I'm curious and keeping an eye on Nix but still haven't tried it, think it's still green for prod use. That said, just re #ansible: many files means composable and modular configs, a big win. I want this to be able to build on the efforts of others and contribute towards sets of shared configs, a commons for sysadmin, just like for other types of code. Takes some work and organization, but good and well maintained sets of is where i want to go. Check out #debops for an example

@wholegroanoats
Sounds good to me. Diff choice here: #ansible as config mgmt, using the excellent #debops playbooks. I want to drive my servers from my machine directly, without a mgmt server, and I want to build on the work of others and contribute my changes, towards a shared commons of server and services configuration.
#selfhost #sysadmin

Has anyone had experience using #DebOps ?

https://debops.org

Did anybody switch from #DebOps to #guix-system and can share some experiences?

I'm currently using #DebOps for deploying some systems. In its early days I made some major contributions to this project, which are still used.

Anyhow, when watching #ansible performing the setup, task by task, for many, many minutes, I wonder whether this is still the way to go. It feels so redundant, esp. since done tasks are performed several times.

packer-builder-nspawn-debootstrap v1.1.0 is out with a bunch of fixes and improvements:
https://git.sr.ht/~angdraug/packer-builder-nspawn-debootstrap

Biggest improvement is the new packer-provisioner-apt plugin that will pre-populate APT's cache, install additional sources and their keys, and run apt-get with all the options it expects in a headless mode.

#DebOps just got a little bit easier.

@toaskoas
Als FISI könnten Dinge wie automatisches Deployment interessant sein, und damit Tools wie #Ansible - und die Sammlung von Absible-Rezepten #debops.

@tpokorra Habe Deinen Blogbeitrag "Migrating a forum from #Discourse to #Flarum" gelesen. Nachdem ich heute einige Stunden versucht habe, eine #ansible, bzw #debops Rolle für discourse zu erstellen, wäre ich für Alternaticen offen.

Was mich abschreckt: flarum ist noch immer Beta, noch nicht mal 0.1.

Wie sind Deine Erfahrungen damit?

https://www.pokorra.de/2018/10/migrating-a-forum-from-discourse-to-flarum/