# Update private plugin without rebuilding the application

**URL:** https://meta.discourse.org/t/update-private-plugin-without-rebuilding-the-application/63286
**Category:** Support
**Created:** [May 24, 2017, 2:44pm UTC](https://meta.discourse.org/t/update-private-plugin-without-rebuilding-the-application/63286 "2017-05-24T14:44:44Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![net\_deamon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/net_deamon/32/70126_2.png) [@net\_deamon](https://meta.discourse.org/u/net_deamon)
#### Post date: [May 24, 2017, 3:15pm UTC](https://meta.discourse.org/t/update-private-plugin-without-rebuilding-the-application/63286/3 "2017-05-24T15:15:07Z")

</div>

It means I will have to spawn another container. Update the other one, and then close this container?

You are talking something like this?

> [@Multiple Discourses, multiple containers, one server](https://meta.discourse.org/t/multiple-discourses-multiple-containers-one-server/35367):
>
> Despite [at least one reference which purports to describe the process](https://meta.discourse.org/t/multisite-configuration-with-docker/14084) I found it very difficult to work out how to run multiple Discourse instances on the same hosting infrastructure (using an instance of nginx running on the host to proxy the Discourse instances). Apparently there’s a way to run Discourse in a “multisite” mode, with multiple instances from a single code installation, but I have not yet seen a real description of how that works. I’ve gone the route of two independent code inst…

---

_[View the full topic](https://meta.discourse.org/t/update-private-plugin-without-rebuilding-the-application/63286)._