Fix Docker Build when USE_EDGE=true #1114
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
Please test latest wekanteam docker image after it's built, does this really fix it for you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This kind-of fixes #1110, but only if you build your Dockerfile with USE_EDGE=true. The wekanteam/wekan:latest on Docker Hub still has the double-slash bug.
Note that the changes are: fixed a path from /home/wekan/packages to /home/wekan/.meteor/packages; and commented out the 'api.versionsFrom(...)' code in package.js for both kadira-flow-router and meteor-useraccounts-core. I know nothing about Meteor so there may be a better way to fix this, but the change got it to where my Dockerfile would build, and now there is no double-slash issue.
This change is