Differences

This shows you the differences between two versions of the page.

--- administration:security [2015/12/14 20:22] – [Changing the Solr Port Number] demiankatz
+++ administration:security [2016/04/25 15:11] – [Changing the Solr Port Number] demiankatz
@@ Line 15: / Line 15: @@
 </code>
-IMPORTANT: If you change VuFind to run under SSL, don't forget to adjust your base URL in [[:config.ini]] accordingly.
+IMPORTANT: If you change VuFind to run under SSL, don't forget to adjust your base URL in [[configuration:files:config.ini]] accordingly.
 ===== Locking Down Solr =====
@@ Line 24: / Line 24: @@
 ==== Changing the Solr Port Number ====
-If necessary, you can change the port number used by Solr by following these steps:
+:!: If using VuFind 3.0 or newer, the Solr port number is controlled by the SOLR_PORT environment variable; just set this before [[administration:starting_and_stopping_solr|starting Solr]] and the server will run on the desired port.
+If using VuFind 2.x or earlier, you can change the port number used by Solr by following these steps:
 === 1. Reconfigure Jetty ===
@@ Line 42: / Line 44: @@
 </code>
-Edit the [Statistics] and/or [Index] sections of the [[:config.ini]] file as appropriate:
+Edit the [Statistics] and/or [Index] sections of the [[configuration:files:config.ini]] file as appropriate:
 <code>
 [Statistics]
@@ Line 53: / Line 55: @@
 </code>
-=== 3. Restart VuFind ===
+=== 3. Restart Solr ===
-Restart the VuFind process so the changes can take effect; i.e., in Linux, switch to the VuFind directory and run:
-<code bash>
-./vufind.sh restart
-</code>
+[[administration:starting_and_stopping_solr#restarting_solr_manually|Restart the Solr process]] so the changes can take effect.
 ===== Locking Down the Admin Panel (VuFind 1.x) =====
@@ Line 76: / Line 71: @@
 ===== Locking Down the Admin Panel (VuFind 2.x) =====
-The admin module in VuFind 2.x is less dangerous than the one found in VuFind 1.x.  It no longer uses the Apache-based password protection scheme.  Instead, a new [AdminAuth] section in [[:config.ini]] allows access to be restricted by IP range and/or VuFind username.  The entire module can still be disabled using the System/admin_enabled setting if desired.
+The admin module in VuFind 2.x is less dangerous than the one found in VuFind 1.x.  It no longer uses the Apache-based password protection scheme.  Instead, a new [AdminAuth] section in [[configuration:files:config.ini]] allows access to be restricted by IP range and/or VuFind username.  The entire module can still be disabled using the System/admin_enabled setting if desired.
 ===== Securing User Credentials =====
-VuFind stores some user information in its database.  Starting with VuFind 2.0RC1, you have the option to perform extra hashing/encryption to protect these credentials.  The settings are off by default in [[:config.ini]], but they can be enabled through VuFind's auto-configuration pages.  Enabling security is highly recommended, but since it breaks backward-compatibility with VuFind 1.x, it should only be done after you are committed to moving forward permanently to 2.x.
+VuFind stores some user information in its database.  Starting with VuFind 2.0RC1, you have the option to perform extra hashing/encryption to protect these credentials.  The settings are off by default in [[configuration:files:config.ini]], but they can be enabled through VuFind's auto-configuration pages.  Enabling security is highly recommended, but since it breaks backward-compatibility with VuFind 1.x, it should only be done after you are committed to moving forward permanently to 2.x.
 ---- struct data ----
 ----