Cool! What do you you see as the advantages of using the ansible-discourse-updater? I’m wondering whether and how we can integrate automation like this into the update service @Eli has been working on.
Having a clear recipe for what should happen at an update, which is always followed by Ansible, is one of the main advantages. There’s not forgetting to do some part of it or getting distracted mid-task. Bear in mind that not everyone agreed with what I have in my ansible playbook here, when I posted it on Meta. Feedback very welcome and a safe, reproducible updater tool that we can all use and trust would be a nice output.
Updating multiple servers from a single command. When you have 9 Discourses to upgrade via the command line, it’s nice to be able to set up Ansible and let it do the work of logging in, running the script, and reporting back to you.
I’ve been using Ansible to update Discourse servers and it is mostly good but as soon as there is an issue you need to revert to doing it manually, these are the tasks I use (the servers have a discourse user):
This was written a couple of years ago when I was first starting to use Ansible and needs a major re-write / refactoring, the most interesting part of it is the Postfix config for using the host to send and receive SMTP email and I do have some work from a client next week to add DKIM support to this using opendkim so I should get a change to update the rest of the repo at the same time.