-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[tools/install.sh] not working like before #5244
Labels
Bug
PR or issue introducing/requiring bug fixes (not mutually exclusive with the Feature label)
Comments
maltheism
added
the
Bug
PR or issue introducing/requiring bug fixes (not mutually exclusive with the Feature label)
label
Sep 24, 2019
Related-ish: #5062 |
Opened #5245 to address this. I'm confused about where your config file went though. Why do you need to regenerate it? |
@johnsaigle I usually delete project and then run the install.sh before the install |
Why do you need to regenerate it though? e.g. Are you working on a cloned VM? |
driusan
pushed a commit
that referenced
this issue
Sep 26, 2019
Adds -p flag to mkdir so that the install script won't fail when user_uploads/ already exists (for whatever reason) in doc_repo or data_release. Fixes #5244.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
Bug
PR or issue introducing/requiring bug fixes (not mutually exclusive with the Feature label)
I've been using the tools/install.sh to generate the config.xml inside the project directory.
Changes have been made to install.sh and now the script will stop before making the config.xml file unlike before.
Basically if a "user_uploads" directory already exists and this can be in the document_repository or the data_release module. I would prefer the script to just skip the create directory commands if the directories already exists. Otherwise I have to manually delete the directories before I can run the script again and unlike before.
Also the script is reporting:
The text was updated successfully, but these errors were encountered: