We have multiple developers that develop workflows and use a single n8n instance for the execution per environment - dev, staging, and production.
One of the challenges we have is the code not being common across 3 different n8n environments similar to other SDLC development and GIT policies and PR can not be done.
What can we do and what does the community do for this kind of scenario.
Hey @Bala_Sista,
Can you help me understand this statement?
One of the challenges we have is the code not being common across 3 different n8n environments similar to other SDLC development and GIT policies and PR can not be done
By code do you mean the workflows? Or are you talking about the n8n code?
Can you please explain your scenario in a bit more detail?
Code - Workflows development. not n8n core modules
i guess until versioning is available you will struggle with this task
Yeah I suspect a manual or automated export / import would be the way forward. There is a workflow available that backs up the workflows to Git which could be a good starting point but the manual process would be to treat it like any other application that you can export settings from.
@sirdavidoff Not sure if you are tracking versioning requests but this kind of fits in with some of the bits from our chat.
Absolutely — versioning and environments go hand-in-hand. It’s on the roadmap 