# How do you manage 3 environments in a WeWeb project?

**URL:** <https://community.weweb.io/t/how-do-you-manage-3-environments-in-a-weweb-project/19309>\
**Category:** Ask us anything\
**Created:** [July 19, 2025, 1:27pm UTC](https://community.weweb.io/t/how-do-you-manage-3-environments-in-a-weweb-project/19309 "2025-07-19T13:27:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Temitope.1](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/temitope.1/32/14674_2.png) [@Temitope.1](https://community.weweb.io/u/Temitope.1)\
**Post date:** [July 19, 2025, 1:27pm UTC](https://community.weweb.io/t/how-do-you-manage-3-environments-in-a-weweb-project/19309/1 "2025-07-19T13:27:24Z")

</div>

Hey everyone 👋

I’m curious — is it possible to have three environments in a single WeWeb project?

For example:

1.One for fixing bugs

2.One for testing new features

3.One for clean production

Has anyone set up something like this before? Would love to know how you manage it — and if there’s a best practice or workaround.

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [July 19, 2025, 2:22pm UTC](https://community.weweb.io/t/how-do-you-manage-3-environments-in-a-weweb-project/19309/2 "2025-07-19T14:22:53Z")

</div>

Probably with code export and Github’s branching.

---

<div class="post-metadata">

**Author:** ![thijs](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/thijs/32/13651_2.png) [@thijs](https://community.weweb.io/u/thijs)\
**Post date:** [July 23, 2025, 7:35am UTC](https://community.weweb.io/t/how-do-you-manage-3-environments-in-a-weweb-project/19309/3 "2025-07-23T07:35:29Z")

</div>

Hi @Temitope.1 ,

Not that I know of, but I would very much look forward to better version control indeed.

Especially a way to:

- have a complete list/history of changes since the last published version (recently I noticed a mistake within let’s say 10-20 minutes that I couldn’t undo anymore, so I had to fall back on a backup - and then redo a bunch of stuff).
- put unpublished changes on hold from publishing - to allow another change (e.g. bugfix) to be published inbetween.

In the mean time, I have two suggestions (more like a temporary solution / ‘bandage’) related to separating new features development from production:

- Working with duplicating pages in Weweb project to make changes and test - so it can’t directly affect production. But I’ve heard people saying that publishing changes may cause bugs in unrelated areas (I have yet to experience this myself).
- Duplicate/copy your production project - and make changes in that duplicate. When tested and approved, you can publish and switch your domain/DNS to this project. The only problem with this is that any changes that can’t wait (e.g. bugfix) need to be applied on both projects.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/b/bee40a614c5b74fbef4e7bb6f73d022e2b8203e3.png) [@system](https://community.weweb.io/u/system)\
**Post date:** [October 2, 2025, 1:27pm UTC](https://community.weweb.io/t/how-do-you-manage-3-environments-in-a-weweb-project/19309/4 "2025-10-02T13:27:39Z")

</div>

This topic was automatically closed after 75 days. New replies are no longer allowed.