When deploying compose via git, environment variable injection does not take effect

[LovesAsuna]

To Reproduce

1. A Compose project utilizing environment variable files, specifically for my use case with Weblate.
2. Overwrite environment variable in dokploy

Current vs. Expected behavior

It's clearly due to a conflict between Dokploy's environment variable injection method and compose projects that directly use environment variable files.

Provide environment information

dokploy version：Version v0.27.1

Which area(s) are affected? (Select all that apply)

Docker Compose

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

I learned about Dokploy's environment variable injection mechanism through Dokploy/website#131. Perhaps we should consider merging the environment variable files?

Will you send a PR to fix it?

No

[djsisson]

can you give an example

do you mean, an env listed in the compose file is overwriting what you supply in dokploy, if so that is intentional and is done by docker compose itself
any env listed in the environment section of a compose file take precedence, over any that are merged if you add the env_file key

so lets say in the compose you have

services:
  xxx:
    environment:
      TEST=XXX
    env_file: .env

then in dokploy you add TEST=YYY the service will only ever get XXXX

[LovesAsuna]

This is Weblate's compose file. As you can see, the Weblate service itself references en environment file. The environment variables I want to define don't exist in the environment file, yet they still don't take effect after being configured in Dokploy.

[djsisson]

Change the env file key to .env, it needs to point to to the env file ./environment won't exist in dokploy

[LovesAsuna]

This is the crux of the issue - it's not my personal git project

I don't want to fork a repository just to modify this file

[djsisson]

The compose file just has images, so just paste the compose into dokploy and alter it, no need to use it as a git project
Dokploy will not alter the compose file in a way that would make this work for you.

[LovesAsuna]

You mean I should copy the environment file into dokploy and use raw compose? But I'm concerned this might cause delayed variable updates

[Siumauricio]

This is the crux of the issue - it's not my personal git project

I don't want to fork a repository just to modify this file

Perhaps you are interested in the patches feature that we will be launching in the next version. It will surely help you avoid forking the project. https://x.com/Siumauricio/status/2024040413863010552

I don't see anything to resolve here, so I'll close this for now.