# Playbook Ansible para atualizar Discourses

**URL:** <https://meta.discourse.org/t/ansible-playbook-for-updating-discourses/119268>\
**Category:** Sysadmins\
**Tags:** explanation\
**Created:** [Junho 1, 2019, 10:01am UTC](https://meta.discourse.org/t/ansible-playbook-for-updating-discourses/119268 "2019-06-01T10:01:07Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![pacharanero](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pacharanero/32/500583_2.png) [@pacharanero](https://meta.discourse.org/u/pacharanero)\
**Post date:** [Junho 2, 2019, 11:11am UTC](https://meta.discourse.org/t/ansible-playbook-for-updating-discourses/119268/6 "2019-06-02T11:11:04Z")

</div>

OK thanks @featheredtoast and @marianord

About half the time when I do updates on servers, the next time I log in the MOTD is ‘A reboot is required’, so I had decided that rebooting would probably be necessary most times I run the update.

Very easy to have two playbooks, one which does `dist-upgrade`, `autoclean` and `reboot` and one which does just plain `upgrade`, no `autoclean`, and no `reboot`, maybe?

I tend to trigger these playbooks manually, and watch the output, so they are not running on a `cron` job or on a daily basis, which I would agree is risky in terms of rebooting in the middle of work.

Note that due to the way Discourse works with client-side Ember code, users can be in the middle of writing a reply when the server reboots and they will probably not notice any interruption. Reboots take less than 15secs usually in my setup.

---

_[View the full topic](https://meta.discourse.org/t/ansible-playbook-for-updating-discourses/119268)._