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
Im trying to deploy langflow as a stack using their Github repo, problem is that in their docker-compose.yml they have already defined
env_file:
- .env
So portainer fails to find the .env because the env vars that i passed to the portainer are referenced as stack.env
I know that i can clone the repo edit yml to use stack.env etc but this fails the purpose of using portainer - 3rd party github repos, with updates etc.
Portainer should allow the user to input env vars and also input the .env file name. This wasy for example i could have said to portainer that the stack env file should be named .env and it could have worked.
Maybe i missed something, lets hope the portainer experts will jump in.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Ask a Question!
Hello there,
Im trying to deploy langflow as a stack using their Github repo, problem is that in their docker-compose.yml they have already defined
env_file:
- .env
https://github.com/langflow-ai/langflow/blob/dev/docker-compose.yml
So portainer fails to find the .env because the env vars that i passed to the portainer are referenced as stack.env
I know that i can clone the repo edit yml to use stack.env etc but this fails the purpose of using portainer - 3rd party github repos, with updates etc.
Portainer should allow the user to input env vars and also input the .env file name. This wasy for example i could have said to portainer that the stack env file should be named .env and it could have worked.
Maybe i missed something, lets hope the portainer experts will jump in.
Beta Was this translation helpful? Give feedback.
All reactions