# Application Files after Digital Ocean Setup

**URL:** <https://meta.discourse.org/t/application-files-after-digital-ocean-setup/126005>\
**Category:** Self-hosting\
**Created:** [August 16, 2019, 5:59pm UTC](https://meta.discourse.org/t/application-files-after-digital-ocean-setup/126005 "2019-08-16T17:59:50Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [August 16, 2019, 6:59pm UTC](https://meta.discourse.org/t/application-files-after-digital-ocean-setup/126005/7 "2019-08-16T18:59:40Z")

</div>

> [@sfoster](#):
>
> Just curious, every time we add a plugin we need to ./launcher rebuild app? And then do that again when modify the plugin?

That’s what I do, though you can also do an upgrade via the web interface at `/admin/upgrade`.

Also, a 2-container install lets you upgrade like

```plaintext
./launcher bootstrap web_only
./launcher destroy web_only; ./launcher start web_only

```

so your site is down just as long as it takes the new server to boot up (about a minute).

---

_[View the full topic](https://meta.discourse.org/t/application-files-after-digital-ocean-setup/126005)._