Skip to content
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

docker: allow to configure Invidious by env var #1030

Merged
merged 1 commit into from
Mar 4, 2020

Conversation

leonklingele
Copy link
Contributor

Invidious gained support to read its configuration from an env var
instead of config file in e3c10d7.

Unfortunately, Docker doesn't allow newline characters in env var
values (see 0) which means we can only provide a proper YAML config
by using the inlined configuration in docker-compose.yml which,
unfortunately, is tracked by Git. Once support for multiline env var
values has been added to Docker, we should migrate and read the config
from a .env file instead (which is not tracked by Git).

Invidious gained support to read its configuration from an env var
instead of config file in e3c10d7.

Unfortunately, Docker doesn't allow newline characters in env var
values (see [0]) which means we can only provide a proper YAML config
by using the inlined configuration in docker-compose.yml which,
unfortunately, is tracked by Git. Once support for multiline env var
values has been added to Docker, we should migrate and read the config
from a .env file instead (which is not tracked by Git).

[0]: docker/compose#3527
@leonklingele
Copy link
Contributor Author

Rebased. Please merge once CI is green @omarroth

@omarroth
Copy link
Contributor

omarroth commented Mar 4, 2020

👍

@omarroth omarroth merged commit 3126e1a into iv-org:master Mar 4, 2020
@github-actions
Copy link

This pull request has been automatically locked since there has not been any activity in it in the last 30 days. If you want to tell us about needed or wanted changes or if problems related to this code are discovered, feel free to open an issue or a new pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 10, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants