This repository was archived by the owner on Oct 29, 2020. It is now read-only.
Vagrant solr#2895
Merged
blisteringherb merged 3 commits intoDoSomethingArchive:devfrom Aug 4, 2014
blisteringherb:vagrant-solr
Merged
Vagrant solr#2895blisteringherb merged 3 commits intoDoSomethingArchive:devfrom blisteringherb:vagrant-solr
blisteringherb merged 3 commits intoDoSomethingArchive:devfrom
blisteringherb:vagrant-solr
Conversation
Contributor
|
Pulling this beast down to test 😱 |
Contributor
There was a problem hiding this comment.
Ran this as a test, and i don't have anything in my var/www/vagrant folder. Looking into it with @blisteringherb -- he thinks this may be the culprit.
Contributor
|
@blisteringherb Is this ready to re-test? |
Contributor
Author
|
@aaronschachter Yes, I tested it again on my local, and it ran error-free for me. |
Contributor
|
👍 👯 |
added 3 commits
August 4, 2014 14:32
* Installs tomcat 7 incl. the admin and manager * Installs Jenkins * Installs solr 4.7 multicore with the same configuration as all other environments
* Also turning off Salt verbose mode * Adding line for collection1 in solr.xml to turn on that index in multicore
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What's this PR do?
Where should the reviewer start?
The most significant changes are in the salt provisioning. The old solr config files have been removed and replaced with solr config files in a gist that work for a Drupal Solr 4.7 installation. Tomcat 7 is also installed instead of Tomcat 6. The changes to the tomcat.sls salt file will give a good overview of what needs reviewing.
How should this be manually tested?
127.0.0.1 solr.dev.dosomething.orgto your/etc/hostsfile, check that you can visit solr.dev.dosomething.org:8080/solr and that all of the affiliates solr instances are listed in the drop down.Any background context you want to provide?
Dev boxes currently are set up to connect to the QA Solr instance, but in the case that we actually need to debug search it's better to have a solr instance set up locally.
cc: @mshmsh5000 @aaronschachter