# Properly shut down Discourse when host shuts down

**URL:** <https://meta.discourse.org/t/properly-shut-down-discourse-when-host-shuts-down/34493>\
**Category:** Product Support\
**Created:** [14.Октябрь.2015 10:00:49 UTC](https://meta.discourse.org/t/properly-shut-down-discourse-when-host-shuts-down/34493 "2015-10-14T10:00:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![omfg](https://avatars.discourse-cdn.com/v4/letter/o/5e9695/32.png) [@omfg](https://meta.discourse.org/u/omfg)\
**Post date:** [14.Октябрь.2015 10:35:37 UTC](https://meta.discourse.org/t/properly-shut-down-discourse-when-host-shuts-down/34493/2 "2015-10-14T10:35:37Z")

</div>

Discourse data is written to the host, so whatever has been written, will survive.  
Unless you’re on a very busy Discourse instance, I would say you could simply shutdown now.

On a _very_ busy Discourse instance, I’d stop Nginx and DB (in Docker) manually, then shutdown the app and OS. I’d probably make a script that runs these steps and you can do the same (`sudo ./shtudown-docker.sh` isn’t that hard).

---

_[View the full topic](https://meta.discourse.org/t/properly-shut-down-discourse-when-host-shuts-down/34493)._