Fix postgresql for "vagrant provision" #865
Merged
Conversation
This file contains 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
This is a "proper fix" to allow for the fact that puppet run via vagrant needs to provision postgresql, but puppet run via AWS does not.
|
log of my broken Looks like "Missing setting 'SOLR_SYNONYMS'" (is that just my personal |
|
@jkmarx this should fix the |
Current coverage is
|
jkmarx
added a commit
that referenced
this pull request
Feb 3, 2016
Fix postgresql for "vagrant provision"
|
FTR I deleted the |
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.
The ppostgresql part of
vagrant provisionwas broken (by me).I think this fixes that, but for me
vagrant provisionnow falls over for a different reason, and I'm not sure what's going on.