-
Notifications
You must be signed in to change notification settings - Fork 549
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
environment variables? #8
Comments
We pass exactly the same environment variables to slugs and docker apps. |
Thank you for your answer, I did manage to get |
This is because the |
…ailed heroku#8 [4/7] RUN pip3 install --no-cache-dir -q -r /tmp/requirements.txt heroku#8 2.007 error: externally-managed-environment heroku#8 2.007 heroku#8 2.007 �� This environment is externally managed heroku#8 2.007 ������> heroku#8 2.007 The system-wide python installation should be maintained using the system heroku#8 2.007 package manager (apk) only. heroku#8 2.007 heroku#8 2.007 If the package in question is not packaged already (and hence installable via heroku#8 2.007 "apk add py3-somepackage"), please consider installing it inside a virtual heroku#8 2.007 environment, e.g.: heroku#8 2.007 heroku#8 2.007 python3 -m venv /path/to/venv heroku#8 2.007 . /path/to/venv/bin/activate heroku#8 2.007 pip install mypackage heroku#8 2.007 heroku#8 2.007 To exit the virtual environment, run: heroku#8 2.007 heroku#8 2.007 deactivate heroku#8 2.007 heroku#8 2.007 The virtual environment is not deleted, and can be re-entered by re-sourcing heroku#8 2.007 the activate file. heroku#8 2.007 heroku#8 2.007 To automatically manage virtual environments, consider using pipx (from the heroku#8 2.007 pipx package). heroku#8 2.007 heroku#8 2.007 note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. heroku#8 2.007 hint: See PEP 668 for the detailed specification. heroku#8 ERROR: process "/bin/sh -c pip3 install --no-cache-dir -q -r /tmp/requirements.txt" did not complete successfully: exit code: 1
Hello, is there a documentation for which env variables does heroku pass to the docker and to the app?
I need to access latest commit hash in the app.
The text was updated successfully, but these errors were encountered: