# Discourse ontwikkeling via docker of andere

**URL:** https://meta.discourse.org/t/discourse-development-through-docker-or-other/368054
**Category:** Support
**Created:** [29 mei 2025 om 11:24 UTC](https://meta.discourse.org/t/discourse-development-through-docker-or-other/368054 "2025-05-29T11:24:06Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![Olle11](https://avatars.discourse-cdn.com/v4/letter/o/cdc98d/32.png) [@Olle11](https://meta.discourse.org/u/Olle11)
#### Post date: [29 mei 2025 om 11:24 UTC](https://meta.discourse.org/t/discourse-development-through-docker-or-other/368054/1 "2025-05-29T11:24:06Z")

</div>

Hi,

Whenever I need to add a plugin or edit some setting in PuTTy docker I need to rebuild the container.

Is there a faster way to edit in Docker without having to rebuild?

Best regards  
Olle

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [29 mei 2025 om 11:37 UTC](https://meta.discourse.org/t/discourse-development-through-docker-or-other/368054/2 "2025-05-29T11:37:16Z")

</div>

If you add or remove a plugin you must rebuild.

Btw consider dropping PuTTY in favour of Windows Terminal.

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [29 mei 2025 om 11:44 UTC](https://meta.discourse.org/t/discourse-development-through-docker-or-other/368054/3 "2025-05-29T11:44:53Z")

</div>

Developing plugins against a production site will be a very tedious process. I’d recommend you look at setting up a local (or cloud) development environment. We have a few guides over here:

> [@Developing Discourse using a Dev Container](https://meta.discourse.org/t/developing-discourse-using-a-dev-container/336366):
>
> [Dev Containers](https://containers.dev/) is an open standard for configuring a development environment inside a container. This almost entirely eliminates the need to install/configure Discourse-specific tools/dependencies on your local machine, and makes it very easy to keep up-to-date as Discourse evolves over time. Dev Containers can be used in a number of different IDEs, or directly using their reference CLI. This guide will describe the setup process for VSCode. Getting started [Download and install](https://code.visualstudio.com/) VSCode Ins…

---

<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: [29 mei 2025 om 17:34 UTC](https://meta.discourse.org/t/discourse-development-through-docker-or-other/368054/4 "2025-05-29T17:34:27Z")

</div>

> [@Olle11](#):
>
> Is there a faster way to edit in Docker without having to rebuild?

It’s not really recommended, but you can do something like

```plaintext
cd /var/discourse
./launcher enter app
cd /var/www/discourse/plugins/your-plugin-path
git pull
sv restart unicorn

```

But unless you’re changing something pretty trivial you’ll want to set up a development environment as suggested.

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [29 mei 2025 om 19:15 UTC](https://meta.discourse.org/t/discourse-development-through-docker-or-other/368054/5 "2025-05-29T19:15:57Z")

</div>

But that’s not going to run any migrations?

---

<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: [29 mei 2025 om 19:36 UTC](https://meta.discourse.org/t/discourse-development-through-docker-or-other/368054/6 "2025-05-29T19:36:11Z")

</div>

I’m assuming that if he doesn’t know any more than he seems to that there aren’t going to be any migrations. 🤷

But, yeah, if it were you, then I would have said to also

```plaintext
bin/rails db:migrate

```

And then you’d say “but what about assets?”

And I’d say, “Yeah, you need to do that too. Exactly how is left as an exercise to the reader.”

---

<div class="post-metadata">

### Author: ![Olle11](https://avatars.discourse-cdn.com/v4/letter/o/cdc98d/32.png) [@Olle11](https://meta.discourse.org/u/Olle11)
#### Post date: [30 mei 2025 om 00:43 UTC](https://meta.discourse.org/t/discourse-development-through-docker-or-other/368054/7 "2025-05-30T00:43:33Z")

</div>

Hmm maybe I should just do it like I use to so I don’t break the site,

Is Windows Terminal better to use than PuTTY?

Best regards  
Olle

---

<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: [30 mei 2025 om 09:30 UTC](https://meta.discourse.org/t/discourse-development-through-docker-or-other/368054/8 "2025-05-30T09:30:27Z")

</div>

> [@Olle11](#):
>
> maybe I should just do it like I use to so I don’t break the site,

If you move to a new server, you’ll make no changes to the site until you know the new site works. It’s impossible to break the site.

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [30 mei 2025 om 09:31 UTC](https://meta.discourse.org/t/discourse-development-through-docker-or-other/368054/9 "2025-05-30T09:31:36Z")

</div>

> [@Olle11](#):
>
> Is Windows Terminal better to use than PuTTY?

Yes, it’s much more modern.

Windows Terminal offers multiple tabs, customizable themes, Unicode and UTF-8 support, GPU acceleration, and better integration with modern Windows features compared to PuTTY.

Windows Terminal integrates with Windows Subsystem for Linux (WSL), supports native shell profiles, and allows seamless switching between PowerShell, Command Prompt, and WSL environments within a single window.
