n8n/packages/cli/src/environments.ee
Charlie Kolb 9f2efb75aa
feat(core): Introduce workflowPublishHistory table (no-changelog) (#22043)
Co-authored-by: Ricardo Espinoza <ricardo@n8n.io>
2025-11-28 14:57:38 +01:00
..
source-control feat(core): Introduce workflowPublishHistory table (no-changelog) (#22043) 2025-11-28 14:57:38 +01:00
variables feat(core): Handle project variables sync on source control (#21001) 2025-10-22 10:26:22 +02:00
README.md chore: Add local development docs for environments feature (#20165) 2025-09-30 09:44:09 +02:00

Environments

Environments enable enterprise users of n8n to effectively manage multiple deployments of n8n by synchronizing them using a shared git repostiory.

Link to docs

Local development

When using the "usual" pnpm run dev scripts to start a local n8n instance, your local git settings and credentials will be picked up by the git repository that is cloned within n8n.

This is why you should start n8n in a docker container when doing any kind of manual testing of this feature.

Building a local docker image from your local checkout: pnpm build:docker

Starting a local container using that image: pnpm --filter n8n-containers stack:enterprise

The development experience of running n8n from source in a docker container still leaves a lot to be desired (lots of waiting for building and running the container). We should improve on this in the future.