# Using dv (Discourse Vibe) to configure Discourse AI in development

**URL:** https://meta.discourse.org/t/using-dv-discourse-vibe-to-configure-discourse-ai-in-development/388622
**Category:** Development
**Created:** [November 17, 2025, 3:44am UTC](https://meta.discourse.org/t/using-dv-discourse-vibe-to-configure-discourse-ai-in-development/388622 "2025-11-17T03:44:03Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [April 6, 2026, 11:40pm UTC](https://meta.discourse.org/t/using-dv-discourse-vibe-to-configure-discourse-ai-in-development/388622/4 "2026-04-06T23:40:04Z")

</div>

> [@BrianC](#):
>
> Does this need to be installed first and then install new discourse instances and configure or could it be installed to work with existing installations and then add more.

dv tries to be an end-to-end tool. It manages the proxy and everything, for example I keep my instances on XYZ.home.arpa.

You would configure multiple containers with dv and use `dv catchup` to update them to latest which would take care of updating plugins and core.

At the bottom everything is just docker containers, you can wrestle them into any shape you need, including importing data, running custom commands and so on.

> [@stephtara](#):
>
> Would you mind giving a little more “non-developer” context?

This is very much predominantly a “developer/designer first” environment. You could `dv build` → `dv new something` → `dv ra codex` and work your way around, but this is not attempting to bring engineering to the masses, it is trying to create lots of isolated pods of development on your machine as a power user feature for engineers/designers.

---

_[View the full topic](https://meta.discourse.org/t/using-dv-discourse-vibe-to-configure-discourse-ai-in-development/388622)._