It's been only four weeks and I really love using mise-en-place by @jdx@fosstodon.org So far I've used it for (chronologically):

- 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

Recently found a way to make it easier to save my graphical environment configuration with #Ansible and the like. Before I start adjusting the desktop to my liking, I run:

inotifywait --monitor --recursive ~/.config

This shows me what files are changed when I click "Apply". This way I don't need to wade through pages of config file documentation, but I still know what I need to reproduce.

Finally back online after reworking my #selfhosting setup!

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.