How do you manage 3 environments in a WeWeb project?

Ask us anything
1

Hey everyone :waving_hand:

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.

2

Probably with code export and Github’s branching.

1 Like
3

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.