Warning: This page has not been updated in over over a year and may be outdated or deprecated.
playground:playground
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
playground:playground [2014/01/21 18:48] – [4 Set up a new Solr Core - if required] chriskeene | playground:playground [2014/01/21 19:29] – [4 Set up a new Solr Core - if required] chriskeene | ||
---|---|---|---|
Line 87: | Line 87: | ||
===== 3 Setting up the New Instance ===== | ===== 3 Setting up the New Instance ===== | ||
- | After this, follow the same steps that you did on initial [[installation notes|installation]] | + | The following steps should work for most setups but you may need to follow the steps that you did on initial [[installation notes|installation]]. |
- Restart Apache for the new config to take effect. | - Restart Apache for the new config to take effect. | ||
Line 96: | Line 96: | ||
===== 4 Set up a new Solr Core - if required ===== | ===== 4 Set up a new Solr Core - if required ===== | ||
- | Cores hold the searchable records within vufind. Follow these steps if this instance | + | Solr Cores hold the searchable records within vufind. Follow these steps if you want this instance |
- | The most common setup, outlined here is an additional core on the existing Solr instance | + | The most common setup, outlined here is an additional core on the existing Solr instance, though there are other options, see further down this page. |
* Shutdown vufind ($VUFIND_HOME/ | * Shutdown vufind ($VUFIND_HOME/ | ||
Line 138: | Line 138: | ||
It probably does not make sense to try to run two separate instances of Solr on a single server, but if you have a good reason to do this, refer to the old [[..: | It probably does not make sense to try to run two separate instances of Solr on a single server, but if you have a good reason to do this, refer to the old [[..: | ||
+ | |||
+ | ===== Example shell transcript of setting up a new instance ===== | ||
+ | The following example creates a new instance called springfield, | ||
+ | < | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | VuFind has been found in / | ||
+ | |||
+ | Where would you like to store your local settings? [/ | ||
+ | |||
+ | VuFind supports use of a custom module for storing local code changes. | ||
+ | If you do not plan to customize the code, you can skip this step. | ||
+ | If you decide to use a custom module, the name you choose will be used for | ||
+ | the module' | ||
+ | |||
+ | What module name would you like to use? [blank for none] | ||
+ | |||
+ | What base path should be used in VuFind' | ||
+ | |||
+ | When running multiple VuFind sites against a single installation, | ||
+ | to decide how to distinguish between instances. | ||
+ | |||
+ | 1.) Directory-based (i.e. http:// | ||
+ | 2.) Host-based (i.e. http:// | ||
+ | |||
+ | or enter 0 to disable multisite mode. | ||
+ | |||
+ | Which option do you want? 1 | ||
+ | Apache configuration written to / | ||
+ | |||
+ | You now need to load this configuration into Apache. | ||
+ | You can do it in either of two ways: | ||
+ | |||
+ | a) Add this line to your / | ||
+ | | ||
+ | |||
+ | b) Link the configuration to Apache' | ||
+ | ln -s / | ||
+ | |||
+ | Option b is preferable if your platform supports it, | ||
+ | but option a is more certain to be supported. | ||
+ | |||
+ | Once the configuration is linked, restart Apache. | ||
+ | to access VuFind at http:// | ||
+ | |||
+ | For proper use of command line tools, you should also ensure that your | ||
+ | VUFIND_HOME and VUFIND_LOCAL_DIR environment variables are set to | ||
+ | / | ||
+ | |||
+ | |||
+ | libadmin@vufindserver:/ | ||
+ | [sudo] password for libadmin: | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | # edited lines: Alias / | ||
+ | # And: Alias / | ||
+ | libadmin@vufindserver:/ | ||
+ | * Restarting web server apache2 | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | |||
+ | libadmin@vufindserver:/ | ||
+ | |||
+ | libadmin@vufindserver:/ | ||
+ | Shutting down VuFind ... | ||
+ | STOPPED Tue Jan 21 18:45:55 GMT 2014 | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | libadmin@vufindserver:/ | ||
+ | </ | ||
---- struct data ---- | ---- struct data ---- | ||
---- | ---- | ||