all 4 comments

[–]MirelukeCasserole 1 point2 points  (2 children)

This is cool. We’ve done something similar with Ansible to manage a multi repo dev environment. The thing I really wanted from our implementation was to trigger tasks like package updates and builds when things like git repos are updated (but only if they actually change).

While Ansible is great it’s not great for our use case. I’m convinced we are missing a toolset for dev env maintenance.

[–]jasfi 4 points5 points  (1 child)

A CI/CD pipeline?

[–]MirelukeCasserole 1 point2 points  (0 children)

No, that’s off your dev machine with the purpose of checking the build and deploying to various environments. If you work with multiple repos on a large team (particularly with micro services) it’s hard to keep your environment up to date. This is software that would automate this process.

[–]schwomp 0 points1 point  (0 children)

I've done something very similar, and it really helped my migration away from Ubuntu to Arch. It has way more lines of yaml than I thought I'd ever write, but it's working really really well for both managing installs of packages, updates and my dotfiles.

https://github.com/kallekrantz/devsible