Skip to content

Conversation

@Kharonus
Copy link
Member

What are you trying to accomplish?

  • user must be able to adapt those .env files without making changes to the origin

@Kharonus Kharonus requested a review from a team January 30, 2026 08:42
@Kharonus Kharonus self-assigned this Jan 30, 2026
Copy link
Contributor

@NobodysNightmare NobodysNightmare left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 erm... That's not how it works. Or rather how it's intended to work. Also see the docs that I added when introducing this.

The .env file provides default values that Docker Compose will assume, in case an environment variable with the corresponding value can't be found. Otherwise it would assume an empty string for those.

So the .env files have been added to make .local the default TLD, but if you want to customize that, don't touch the env files, but touch your environment.

E.g. in your bashrc (assuming you are a bash user), you could add

export OPENPROJECT_DOCKER_DEV_TLD=internal

(fish is probably similar, but I don't know how)

@Kharonus
Copy link
Member Author

As discussed, I updated the PR with the fallback way of doing stuff. Have a look again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants