From b4eb7e06636c9aac9ecf05f9997e8bbdd8feb3bc Mon Sep 17 00:00:00 2001 From: Steve Sheppard Date: Tue, 14 Dec 2010 17:07:37 -0500 Subject: [PATCH] more updates to bring into line with a real installation attempt; --- 1.6/admin/serversideinstallation.xml | 179 +++++++++++++++++++---------------- 1 file changed, 99 insertions(+), 80 deletions(-) diff --git a/1.6/admin/serversideinstallation.xml b/1.6/admin/serversideinstallation.xml index 8d48568..2160988 100644 --- a/1.6/admin/serversideinstallation.xml +++ b/1.6/admin/serversideinstallation.xml @@ -829,33 +829,36 @@ Download and Unpack Latest Evergreen Version - As the opensrf user, download - and extract the latest version of Evergreen. The latest version can be found here: - + The latest version of Evergreen can be found here: + . + As the opensrf user, change to + the directory /home/opensrf then download + and extract Evergreen. The new subdirectory + /home/opensrf/Evergreen-ILS-1.6.1.2 will be created: # as the opensrf user: + cd /home/opensrf wget http://evergreen-ils.org/downloads/Evergreen-ILS-1.6.1.2.tar.gz tar zxf Evergreen-ILS-1.6.1.2.tar.gz - The new directory - /home/opensrf/Evergreen-ILS-1.6.1.2 - will be created. Install Prerequisites to Build Evergreen - In this section you will install and configure a set of prerequisites that - will be used to build Evergreen. In a following step you will actually build the - Evergreen software using the make utility. + In this section you will install and configure a set of prerequisites that will be + used later in and + to build the Evergreen software + using the make utility. As the root user, enter the commands show below to build the prerequisites from the software distribution that you just downloaded and unpacked. Remember to replace [DISTRIBUTION] in the following example with the keyword corresponding to the name of one of the - Linux distributions listed in the following distribution - keywords table . For example, - to install the prerequisites for Ubuntu version 9.10 (Karmic Koala) you would enter this - command: make -f Open-ILS/src/extras/Makefile.install ubuntu-karmic. + Linux distributions listed in the following + distribution keywords table . + For example, to install the prerequisites for Ubuntu version 9.10 (Karmic Koala) you would + enter this command: make -f Open-ILS/src/extras/Makefile.install + ubuntu-karmic. - # as the opensrf user: + # as the root user: cd /home/opensrf/Evergreen-ILS-1.6.1.2 make -f Open-ILS/src/extras/Makefile.install [DISTRIBUTION] @@ -922,32 +925,33 @@ (see ) does not automatically install PostgreSQL. You must install the PostgreSQL server yourself, either on the same system as Evergreen itself or on another system. - If your PostgreSQL server is on a different system, just skip this step. - For further information on manually installing PostgreSQL, visit the official + If your PostgreSQL server is on a different system, just skip this step. + If your PostgreSQL server will be on the same system as your Evergreen + software, then install the required PostgreSQL server packages as follows. + For further information on manually installing PostgreSQL, visit the official PostgreSQL Site. - If your PostgreSQL server will be on the same system as your Evergreen - software, then as the root user - install the required PostgreSQL server packages: For Debian Lenny and - Ubuntu Hardy (8.04): + Ubuntu Hardy (8.04), execute these commands: # as the root user: + cd /home/opensrf/Evergreen-ILS-1.6.1.2 make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_debs_83 For Ubuntu Karmic (9.10) and - Ubuntu Lucid (10.04): + Ubuntu Lucid (10.04), execute these commands: # as the root user: + cd /home/opensrf/Evergreen-ILS-1.6.1.2 make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_debs_84 PostgreSQL versions 8.3 or 8.4 are the recommended versions to work - with Evergreen 1.6. If you have an older version of PostgreSQL, you should - upgrade before installing Evergreen. To find the running version of + with Evergreen 1.6.1.2 . If you have an older version of PostgreSQL, you + should upgrade before installing Evergreen. To find the running version of PostgreSQL, as the postgres - user, run the psql. Then type SELECT - version(); to get detailed information about your version - of PostgreSQL. + user execute the command psql, then type + SELECT version(); to get detailed information + about your version of PostgreSQL. @@ -1009,10 +1013,11 @@ Configure Evergreen - As the opensrf user, return to - the Evergreen build directory and use the configure and + In this step you will use the configure and make utilities to configure Evergreen so it can be compiled - and linked in the next step: + and linked later in . + As the opensrf user, return to + the Evergreen build directory and execute these commands: # as the opensrf user: cd /home/opensrf/Evergreen-ILS-1.6.1.2 @@ -1020,7 +1025,7 @@ make - + Compile, Link and Install Evergreen In this step you will actually compile, link and install Evergreen and the default Evergreen Staff Client. @@ -1039,12 +1044,12 @@ The above commands will create a new subdirectory /openils/var/web/xul/rel_1_6_1_2 containing the Staff Client. - To complete the Staff Client installation, - as the root user create a symbolic link - named server in the head of the Staff Client directory - /openils/var/web/xul that points to the - subdirectory /server of the new Staff - Client build: + To complete the Staff Client installation, as the + root user execute the following commands to + create a symbolic link named server in the head of the Staff Client + directory /openils/var/web/xul that points to the + subdirectory /server of the new Staff Client + build: # as the root user: cd /openils/var/web/xul @@ -1053,14 +1058,14 @@ Copy the OpenSRF Configuration Files + In this step you will replace some OpenSRF configuration files that you set up in + when you installed and + tested OpenSRF. You must copy several example OpenSRF configuration files into place after first creating backup copies for troubleshooting purposes, then change all the file ownerships - to opensrf. These files replace the - configuration files that you set up in a previous step - (see ) - when you installed and tested OpenSRF. - As the root user, execute the - following commands: + to opensrf. + As the root user, execute the following + commands: # as the root user: cd /openils/conf @@ -1101,7 +1106,7 @@ createlang plperlu evergreen createlang plpgsql evergreen - Continue as user postgres + Continue as the postgres user and execute the SQL scripts as shown below, adjusting the paths as needed, where [PGSQL_VERSION] is your installed PostgreSQL version (e.g. 8.3). @@ -1119,7 +1124,7 @@ named evergreen and assign a password: - # as the root user: + # as the postgres user: createuser -P -s evergreen Enter password for new role: MYNEWPASSWORD Enter it again: MYNEWPASSWORD @@ -1127,15 +1132,13 @@ Create database schema - As the root - user, create the database schema and configure your system with - the corresponding database authentication details for the - evergreen database user that you just created - in the previous step - (see ). - Enter the following commands and replace - HOSTNAME, PORT, PASSWORD and - DATABASENAME with appropriate + In this step you will create the database schema and configure your + system with the corresponding database authentication details for the + evergreen database user that you just created in + . + As the root user, enter + the following commands and replace HOSTNAME, PORT, + PASSWORD and DATABASENAME with appropriate values: # as the root user: @@ -1149,11 +1152,8 @@ localhost and PORT will be 5432. Of course, values for PASSWORD and - DATABASENAME must match the values you used in the - previous step - (see ) - when you created the database and and set a password for the - evergreen user. + DATABASENAME must match the values you used in + . As the command executes, you may see warnings similar to: ERROR: schema SOMENAME does not exist (in fact, you may see one warning per schema) but they can be safely ignored. @@ -1214,20 +1214,24 @@ Create a Security Certificate - You must create a new Security Certificate (SSL Key) for - the Apache server using the openssl - command. For a public production server you must configure or - purchase a signed SSL certificate, but for now you can just use - a self-signed certificate and accept the warnings in the Staff - Client and browser during testing and development. As the - root user, perform the - following commands: + In this step you will create a new Security Certificate (SSL Key) + for the Apache server using the openssl command. For a + public production server you must configure or purchase a signed SSL + certificate, but for now you can just use a self-signed certificate and + accept the warnings in the Staff Client and browser during testing and + development. As the root user, + perform the following commands: # as the root user: mkdir /etc/apache2/ssl cd /etc/apache2/ssl openssl req -new -x509 -days 365 -nodes -out server.crt -keyout server.key + You will be prompted for several items of information; enter + the appropriate information for each item. The new files + server.crt and server.key will + be created in the directory + /etc/apache2/ssl . This step generates a self-signed SSL certificate. You must install a proper SSL certificate @@ -1271,9 +1275,11 @@ should not do this since the conflict does not apply to that operating system. - The following updates are needed to allow the logs + + The following updates are needed to allow the logs to function properly, but it may break other Apache - applications on your server:For the + applications on your server: + For the Linux distributions Ubuntu Hardy or Debian Etch, as @@ -1281,14 +1287,27 @@ edit the Apache configuration file /etc/apache2/apache2.conf and change the line User www-data to User - opensrf. For the + opensrf. + For the Linux distributions Ubuntu Karmic, Ubuntu Lucid or Debian Lenny, as the root user, edit the Apache configuration file and change these - lines:# as the root user:export APACHE_RUN_USER=www-dataexport APACHE_RUN_GROUP=www-datato instead read:# as the root user:export APACHE_RUN_USER=opensrfexport APACHE_RUN_GROUP=opensrf + lines: + + # as the root user: + export APACHE_RUN_USER=www-data + export APACHE_RUN_GROUP=www-data + + to instead read: + + # as the root user: + export APACHE_RUN_USER=opensrf + export APACHE_RUN_GROUP=opensrf + + As the root user, @@ -1432,15 +1451,15 @@ - - Create Configuration Files for Users Needing <command>srfsh</command> - When OpenSRF was installed in a previous step (see - for further information), - the software installation automatically created a utility named - srfsh (surf shell). This is a command line diagnostic tool - for testing and interacting with OpenSRF It will be used - in a future step to complete and test the Evergreen installation. See - for further information. + + (OPTIONAL) Create Configuration Files for Users Needing <command>srfsh</command> + When OpenSRF was installed in , the + software installation automatically created a utility named srfsh (surf + shell). This is a command line diagnostic tool for testing and interacting with + OpenSRF. It will be used in a future step to complete and test the Evergreen installation. + Earlier in you also created a configuration + file ~/.srfsh.xml for each user that might need to use the utility. + See for further information. Modify the OpenSRF Environment @@ -1465,7 +1484,7 @@ . ~/.bashrc - + (OPTIONAL) Enable and Disable Language Localizations You can load translations such as Armenian (hy-AM), Canadian French (fr-CA), and others into the database to complete the translations available in -- 2.11.0