Fix docker-compose dev env for latest ocis #7054
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This sets all missing environment variables in our docker-compose.yml to make latest ocis launch again.
The ocis config path that was checked in our custom entrypoint is obsolete, it should be /etc/ocis/ocis.yml instead.
But even when the path is fixed:
when the file exists, but our environment variables are incomplete, ocis tells us to run ocis init, which then fails because the file already exists.
@dragonchaser suggested we might setup a drone cron pipeline that syncs the env variables set here https://github.com/owncloud/ocis/blob/master/.vscode/launch.json to our docker-compose.yml file or to a .env file.
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist:
Open tasks: