I've been a Linux user for some 10 years, but have also had to use a Macbook Pro for a while due to work. There's nothing stopping you from fully configuring macOS through a single repository similar to how you do Linux. For a while my dot files were aimed at Linux (primarily), macOS, and Windows as I anticipated to have to use both macOS and Windows down the line, though I've since removed much of the multiplatform code.
> This could be an interesting way to run mautrix-imesssage
Wouldn't you be able to have only a single identity? Because unless you can have multiple identities with a single instance, it would be a very expensive way of having iMessage capabilities.
In much of Europe commas are thousand separators, dots are decimal point separators. So what you're seeing is fifty eight euros and thirty one euro-cents.
Many of the automation tools aren't great, but some are better than others. I'd take terraform and puppet or chef over ansible any day. I'd much rather have something that is declarative and easy to make idempotent over something that by design is procedural and much harder to make idempotent. Even bash easier to make idempotent. Don't forget yaml hell that ansible loves to put you in. If there was a tool that had a planning and apply phase for server management like terraform, I'd take that (for pets only). Ansible's dry run barely works since it requires additional effort to get working properly, often impossible without faking data. It's been a while since I've used chef or puppet and I can't remember if their dry run or the like is useful.
Having said that, in an ideal scenario, you use auto scaling combined with cloud init to avoid having to manage live servers. Cattle, not pets. That way you can provision images using chef/puppet, and then have them deploy and be automatically deployed. It gives also gives you the opportunity to create self healing architecture that requires less baby sitting.
K8s certainly forces you to think closer to that architecture and that is good.
I wouldn't. I said that as a point the ansible is bad. It is procedural and hard to follow. Bash and python don't have any host management features (I.e. inventories) so you'd have implement that yourself, which won't be easy.
I suggest looking into the alternative, such as chef, puppet, saltstack etc. They allow for declarative configurations and make it a lot easier to make your configurations idempotent. On top of that, do the infrastructure itself (aws, gcp etc) in terraform (or pulumi if you want it in a programming language). Terraform has its issues, but it is certainly a lot better at managing infrastructure than ansible.
> It seems likely you are coming at this from the perspective of "when I find an ansible playbook on github its hard to follow whats going on".
No, I've worked with ansible over 3 jobs, for the past 4 years. It hasn't been hard to convince colleagues to move away from Ansible once I show the competition. Sadly the migration process is rarely easy.
Ansible is abysmal. I don't know why anyone still chooses it. It's a mess of yaml and what feels like a million yaml files that is always extremely hard to follow. Honestly writing some python, or bash is a lot easier to follow, read, and understand. The only thing it has going for it is the inventory system. I wish ansible would die already.
The tips mentioned in the article are helpful, but still beyond the initial development of roles, maintaining roles is a pain no one can alleviate. It is the perl of automation. I wish people would stop using it. I've yet to start a job where people haven't regretted going towards ansible.
Here in the UK _most_ of the people I met at university didn't know gap years were an option. Post university it's been the same. The few who do take it absolutely love it. I personally didn't know either until I met a few people at university who got to the UK through the Erasmus programme.
It's sad really. As a young person this is the time to be able to do it. Often as you get older life gets in the way. I've been wanting to do it ever since I found out about it but every time something else has gotten in the way. If you're young and reading this, and everything has aligned for you, take a gap year or two.
[0] https://extensions.gnome.org/extension/1486/extensions-sync/