You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using the --project-directory flag to store all our docker compose related files in a .docker directory.
The frameworks we're using in our web projects are all using the dotenv mechanism but we decided that having a single env file containing both docker related variables and app related variables was not the road we wanted to take.
If a PROJECT_DIRECTORY variable was supported, it would save us some keystrokes. While we took the habit of hiding some of the complexity in Makefiles for example, we are still bound to type a full docker compose command at some point.
Thanks in advance !
The text was updated successfully, but these errors were encountered:
I would also love to see this feature implemented, it would simplify the usage when using "docker compose" in a container, because it's easier to pass environment variables than messing with the command-line especially when we can't put this parameters after the "command" word.
Description
Hi !
We're using the
--project-directory
flag to store all our docker compose related files in a.docker
directory.The frameworks we're using in our web projects are all using the dotenv mechanism but we decided that having a single env file containing both docker related variables and app related variables was not the road we wanted to take.
If a
PROJECT_DIRECTORY
variable was supported, it would save us some keystrokes. While we took the habit of hiding some of the complexity in Makefiles for example, we are still bound to type a full docker compose command at some point.Thanks in advance !
The text was updated successfully, but these errors were encountered: