@sven222 @Seraphyn @hosebei

Bin auf NixOS umgestiegen und habe Ansible auf die Seite gelegt...

#ansible #nixos

When talking about open-source virtualization platforms, Proxmox VE is probably one of the first solutions that comes to mind. It combines KVM virtual machines, LXC containers, storage, networking and clustering behind a convenient management interface.
But what if you want to build the same kind of environment on FreeBSD?
This is exactly where Sylve becomes interesting.

https://gyptazy.com/blog/sylve-freebsd-ansible-module-automation/

#freebsd #ansible #automation #cicd #bsd #runbsd

As people kept asking for the modules I developed for my @BoxyBSD@bsd.cafe project, I just made them shiny and prepared them for pushing them upstream.

Making the switch easier for people coming from #Proxmox, it uses mostly the same syntax as the Proxmox modules to keep the interface similar. Next to this, they're built in an equal way with a shared authentication module util, to make sure new modules can directly use the same authentication lib.

Currently it comes:
.
├── LICENSE
├── module_utils
│   └── sylve_common.py
├── modules
│   ├── sylve_jail.py
│   └── sylve_vm.py

#RUNBSD #FREEBSD #SYLVE #BHYVE #VM #JAIL #JAILS

☁️ WARSZTATY: OpenStack-Ansible (OSA) – wdrożenie chmury prywatnej

Adam Lis, specjalista DevOps i entuzjasta #FLOSS, pokaże jak wdrożyć prywatną chmurę #OpenStack przy użyciu #Ansible. W trakcie warsztatów uczestnicy przejdą przez instalację środowiska All-In-One oraz zobaczą, jak przywracać działanie infrastruktury po awarii.

📍 Gdzie? Wydział Matematyki i Informatyki UAM w Poznaniu
📅 Kiedy? 30.05.2026

👉 Sprawdź agendę: https://piwo.sh
🎟️ ODBIERZ BILET: https://app.evenea.pl/event/piwo2026/
#piwo2026

Alt...

Grafika z fioletowym tłem z napisem „Poznańska Impreza Wolnego Oprogramowania”, zdjęcie prelegenta w centralnej części, poniżej pomarańczowe nazwisko „Adam Lis” i biały tekst: „OpenStack‑Ansible (OSA) wdrożenie chmury prywatnej”, po bokach białe rysunki postaci ze świata Open Source.

- switching between #Zig versions, I liked it more than the dedicated anyzig
- #Python venv activation – it's silly but feels so good, and collaborates with uv
- ensuring I have the right language server and formatter for a project, be it #Lua, #TypeScript, and trying out various options for Python
- setting LANG="C.UTF-8" only in the specific project folder because #Ansible refused to work with Polish...

The final boss was getting a really comfortable Tree-sitter setup: get the #Rust CLI, write grammar in #JavaScript, re-generate and run tests on source change as a mise Task. And then I only cloned the repo on another machine and was ready to go!

This post was written as a more cultured outlet for my excitement instead of aggresively committing mise.toml into every repository I touch

inotifywait --monitor --recursive ~/.config

This time it's #Debian with #Docker. I used to avoid containers, preferring to run services directly instead. But setting up backups made me appreciate the separation between the application data in image and persistent state in mounted volumes. The final piece that convinced me is the ability to self-host my own container registry with @forgejo@floss.social

I'm doing the initial setup through #Ansible (learned from @notthebee@tilde.zone), but specific applications are managed via dockge. The ambition to do every adjustment through playbooks burns out really fast when working with a single instance.