one compose with two env files

[lordraiden]

Ask a Question!

I have repository in github with this structure

.env

/ComposeA/docker-compose.yaml

/ComposeA/.env

The first .env is shared with other compose projects, and is a level up of ComposeA

It is possible with the portainer integration with GitHub to create a stack with this setup, one compose with two env files?

[Nick-Portainer]

When using Git repositories in Portainer, it’s best to have one repository per project. If multiple stacks rely on the same repository, any changes made for one stack (e.g., Stack 1) will trigger updates for all stacks using that repository. This means that, if configured to do so, Stack 2 would also redeploy automatically. For this reason, a dedicated repository per stack is ideal.

[lordraiden]

I manage the redeploys via webhook or manually, so it shouldn't be an issue, i guess