We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In https://docs.seek4science.org/tech/docker/docker-compose.html#using-a-sub-uri it mentions editing docker-compose.yml to set RAILS_RELATIVE_URL_ROOT.
docker-compose.yml
RAILS_RELATIVE_URL_ROOT
This could cause conflicts etc. when upgrading, so it would be better to keep such changes in another .env file that is not under version control.
It is possible to reference multiple env_files in docker-compose, so we could have something like:
env_file
env_file: - docker/db.env - .env
and recommend the user creates .env and puts any custom variables in there.
.env
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In https://docs.seek4science.org/tech/docker/docker-compose.html#using-a-sub-uri it mentions editing
docker-compose.yml
to setRAILS_RELATIVE_URL_ROOT
.This could cause conflicts etc. when upgrading, so it would be better to keep such changes in another .env file that is not under version control.
It is possible to reference multiple
env_file
s in docker-compose, so we could have something like:and recommend the user creates
.env
and puts any custom variables in there.The text was updated successfully, but these errors were encountered: