From: Dan Wells Date: Wed, 24 Oct 2018 21:51:41 +0000 (-0400) Subject: Bumping version numbers, adding Upgrade Script and Changelog X-Git-Url: https://old-git.evergreen-ils.org/?a=commitdiff_plain;h=96f36938d6fe19b2bc5b7d92ce9b83e0e6090225;p=evergreen%2Fpines.git Bumping version numbers, adding Upgrade Script and Changelog Signed-off-by: Dan Wells --- diff --git a/ChangeLog b/ChangeLog index 1f72b2c73e..b05e6030ec 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,472 @@ -Evergreen doesn't keep a GNU-style ChangeLog except in release tarballs. -Those seeking a change log are encouraged to run 'git log -v', or read -it online at: http://git.evergreen-ils.org/?p=Evergreen.git;a=log +commit 4939db669d8d9efe8ca8bdda9d9ea12a90c933a8 +Author: Dan Wells +Date: Wed Oct 24 17:32:39 2018 -0400 + + Update Upgrade Docs + + Signed-off-by: Dan Wells + +16 16 docs/installation/server_upgrade.adoc + +commit d86d21dc9b732ea3b70fc5d17283c7b1c1523fc2 +Author: Dan Wells +Date: Mon Feb 24 12:09:57 2014 -0500 + + Bump OpenILS.pm version + + Signed-off-by: Dan Wells + +1 1 Open-ILS/src/perlmods/lib/OpenILS.pm + +commit 06974bf1c30783ccb935cf7910c07984a05a2aec +Author: Dan Wells +Date: Wed Oct 24 17:22:03 2018 -0400 + + Translation updates - po files + + Signed-off-by: Dan Wells + +8 5 build/i18n/po/db.seed/cs-CZ.po +3 3 build/i18n/po/fm_IDL.dtd/cs-CZ.po +4 4 build/i18n/po/lang.dtd/cs-CZ.po +156 97 build/i18n/po/webstaff/ar-JO.po +177 118 build/i18n/po/webstaff/cs-CZ.po +143 90 build/i18n/po/webstaff/en-GB.po +156 97 build/i18n/po/webstaff/es-ES.po +149 96 build/i18n/po/webstaff/hy-AM.po +143 90 build/i18n/po/webstaff/ru-RU.po + +commit df8d10bcaedada490005e76d9c04371193a502ae +Author: Dan Wells +Date: Wed Oct 24 16:42:01 2018 -0400 + + Translation updates - newpot + + Signed-off-by: Dan Wells + +52 39 build/i18n/po/webstaff/webstaff.pot + +commit d8386e7c669de9e020c3b5b2bf5547014bc8633b +Author: Jane Sandberg +Date: Wed Oct 24 09:35:50 2018 -0700 + + Docs: adding another entry to 3.2.1 release notes + + Signed-off-by: Jane Sandberg + +3 0 docs/RELEASE_NOTES_3_2.adoc + +commit b31c51d24a6f9fc307d36f258abf8fae4dd58029 +Author: Jane Sandberg +Date: Wed Oct 24 09:33:23 2018 -0700 + + Docs: adding another entry to 3.1.7 release notes + + Signed-off-by: Jane Sandberg + +3 0 docs/RELEASE_NOTES_3_1.adoc + +commit b395739a6adb98b4c8a6f9166666d6066adb422d +Author: Bill Erickson +Date: Mon Oct 15 11:43:33 2018 -0400 + + LP#1797923 Browser client iframe initial loading page + + Apply a default value to the browser client iframe URL so the iframe + does not attempt to load a copy of the current page. The default value + points to a simple loading page, displying "Loading..." plus our + standard spinny gif. + + Progress gif copied from web/opac/images/ to web/images/ to avoid + dependence on the old opac directory. + + Signed-off-by: Bill Erickson + Signed-off-by: Jason Boyer + Signed-off-by: Galen Charlton + +9 0 Open-ILS/src/templates/staff/loading.tt2 +5 2 Open-ILS/src/templates/staff/share/t_eframe.tt2 +- - Open-ILS/web/images/progressbar_green.gif +20 0 Open-ILS/web/js/ui/default/staff/services/eframe.js + create mode 100644 Open-ILS/src/templates/staff/loading.tt2 + create mode 100644 Open-ILS/web/images/progressbar_green.gif + +commit 5444b765686466d6c64e2c9d60ec041cf6477ac4 +Author: Jane Sandberg +Date: Wed Oct 24 09:15:44 2018 -0700 + + Docs: Adding release notes for 3.2.1 + + Signed-off-by: Jane Sandberg + +38 4 docs/RELEASE_NOTES_3_2.adoc + +commit 03e3591bf090cf76b7778878ae73a64e0719139f +Author: Jane Sandberg +Date: Wed Oct 24 09:02:37 2018 -0700 + + Docs: adding release notes for 3.1.7 + + Signed-off-by: Jane Sandberg + +34 0 docs/RELEASE_NOTES_3_1.adoc + +commit b14f00f1da0eaedf72d74b2bb623b2033001d32d +Author: Jason Stephenson +Date: Tue Oct 23 16:32:17 2018 -0400 + + Forward port 3.1.5-3.2.0-upgrade-db.sql. + + Signed-off-by: Jason Stephenson + +4904 0 Open-ILS/src/sql/Pg/version-upgrade/3.1.5-3.2.0-upgrade-db.sql + create mode 100644 Open-ILS/src/sql/Pg/version-upgrade/3.1.5-3.2.0-upgrade-db.sql + +commit 20c9ab2b82187ff2631e778d8b9e503362d1c19c +Author: Kathy Lussier +Date: Wed Sep 26 14:45:26 2018 -0400 + + LP#1746536: Remove input-group-addon class from Add Call Number button + + The button no longer looks like a button with this class in place. + + Signed-off-by: Kathy Lussier + Signed-off-by: Galen Charlton + +1 1 Open-ILS/src/templates/staff/cat/volcopy/t_edit.tt2 + +commit b85f23609861f89a0934facdc85cb3ae06b6e57d +Author: Mike Rylander +Date: Wed Sep 26 12:57:04 2018 -0400 + + LP#1746536: Restrict CN addition but allow CN edits... + + ... in the top half of the Vol/Copy editor when there are multiple bib records + represented in the UI. + + Also, restrict the size of the org selector using a bootstrap row. + + Signed-off-by: Mike Rylander + Signed-off-by: Kathy Lussier + + Conflicts: + Open-ILS/src/templates/staff/cat/volcopy/t_edit.tt2 + Open-ILS/web/js/ui/default/staff/cat/volcopy/app.js + + Signed-off-by: Galen Charlton + +7 3 Open-ILS/src/templates/staff/cat/volcopy/t_edit.tt2 +8 9 Open-ILS/web/js/ui/default/staff/cat/volcopy/app.js + +commit debbef79a8b33f2805def7a47419151ce911c2b4 +Author: Mike Rylander +Date: Wed Sep 19 10:38:42 2018 -0400 + + LP#1746536: Allow batch-apply to volume fields in multi-record context + + I can't see a reason to restrict Batch Apply for volume fields in a multi- + record context, as all the data is gathered based on the volume owners, not + record information. This commit removes that restriction. + + Signed-off-by: Mike Rylander + Signed-off-by: Galen Charlton + Signed-off-by: Kathy Lussier + Signed-off-by: Galen Charlton + +1 1 Open-ILS/src/templates/staff/cat/volcopy/t_edit.tt2 + +commit 255d7e5ad6dbcaf66b6238788e30bc231ee9f81c +Author: Cesar Velez +Date: Wed Sep 12 05:37:28 2018 -0400 + + LP#1746536 - enable volcopy editor for multi-bib but only volumes + + This removes the disabling of the volcopy editor caused by + passing it a record id of 0. Allowing the Item Status grid's + Edit>Volumes to function as a way to batch edit volumes of + more than 1 bib record. + + Signed-off by: Cesar Velez + Signed-off-by: Mike Rylander + Signed-off-by: Galen Charlton + + Signed-off-by: Kathy Lussier + Signed-off-by: Galen Charlton + +6 5 Open-ILS/web/js/ui/default/staff/cat/volcopy/app.js + +commit e02f1e84143fb090a0db49eb624ae826a626910f +Author: a. bellenir +Date: Wed Jun 27 14:48:56 2018 -0400 + + LP1746536: cannot edit vol/call number in item status + + spawnHoldingsEdit was disabling record summary by passing record_id: 0 + this change will provided the record_id if exactly one record is selected. + behavior is unchanged if multiple records are selected. + + Signed-off-by: a. bellenir + Signed-off-by: cesar velez + Signed-off-by: Mike Rylander + Signed-off-by: Kathy Lussier + + Conflicts: + Open-ILS/web/js/ui/default/staff/circ/services/item.js + + Signed-off-by: Galen Charlton + Signed-off-by: Kathy Lussier + Signed-off-by: Galen Charlton + +16 12 Open-ILS/web/js/ui/default/staff/circ/services/item.js + +commit b1440802e6a0508b6e89020f6bd1e210641208bc +Author: Dan Wells +Date: Wed Oct 10 16:07:24 2018 -0400 + + LP#1796978 Realign working copy refresh with proper condition + + The "working copy" grid needs to update whenever the copy data above + updates. I *believe* this aligns the refresh with its intended + condition. + + This appears to have come about via bug #1732761, so retesting of + that fix may be in order. + + Signed-off-by: Dan Wells + Signed-off-by: Jason Stephenson + Signed-off-by: Cesar Velez + +2 2 Open-ILS/web/js/ui/default/staff/cat/volcopy/app.js + +commit 75f10d164291a64715e766a112cc7c0502861653 +Author: Dan Wells +Date: Thu Oct 11 09:21:05 2018 -0400 + + LP#1796971 Wait for call number and copy before loading locations + + In cases where add a copy to a call number, we fetch the original + call number via async, then attach the new copy to it. Before this + commit, however, we were not waiting for the call number fetch + promise to resolve, so the copy wasn't there to use for limiting the + location load. + + Since the async request is internal to a loop, one way out is to + capture that promise, then make sure it resolves before loading the + locations. + + (We previously returned the copies from the internal function, but that + value wasn't being used anyway, so we don't worry about unwrapping the + $q.all() when it resolves.) + + Signed-off-by: Dan Wells + Signed-off-by: John Amundson + Signed-off-by: Jason Stephenson + Signed-off-by: Cesar Velez + +4 3 Open-ILS/web/js/ui/default/staff/cat/volcopy/app.js + +commit ad11c1b6d89e8690caed7ae02a1fc0a0202954c7 +Author: Remington Steed +Date: Tue Oct 9 10:36:45 2018 -0400 + + Docs: Update release notes version in consolidated manual + + Signed-off-by: Remington Steed + +1 1 docs/root.adoc + +commit a9329bfd9f874811a7f0c5f1364ba0463fe58703 +Author: Bill Erickson +Date: Mon Sep 17 10:18:30 2018 -0400 + + LP#1792658 Angular Evergreen favicon + + Use the Evergreen favicon.ico in the Angular(6) application. + + Signed-off-by: Bill Erickson + Signed-off-by: Galen Charlton + +- - Open-ILS/src/eg2/src/favicon.ico + +commit fa3cd5cc70598a6a749c8b51003088a4b10442c8 +Author: Bill Erickson +Date: Mon Aug 6 15:18:35 2018 -0400 + + LP#1785681 Patron address copy to clipboard + + Support copying formatted addresses to the clipboard in the browser + staff client, similar to the XUL client. Action is performed via a new + link in the addresses section (next to "print") in the patron summary + sidebar. + + Signed-off-by: Bill Erickson + Signed-off-by: Garry Collum + Signed-off-by: Galen Charlton + +16 2 Open-ILS/src/templates/staff/circ/patron/t_summary.tt2 +18 0 Open-ILS/web/js/ui/default/staff/circ/patron/app.js + +commit 22fcbd3497069230a49d339e720b2c882d6dd585 +Author: Galen Charlton +Date: Tue Sep 11 14:58:29 2018 -0400 + + LP#1721139: apply proper date format in certain places + + This patch ensures that the correct date format is used + to display dates in certain contexts in the web staff + client: + + - patron bucket summary + - record bucket summary + - patron bucket 'View batch edits' + + This has the side effect of fixing a problem where the batch + edit timestamps were not wrapped correctly in Firefox. + + To test + ------- + 1. Using user buckets, make some batch changes on some patrons and roll + back some of those changes. + 2. Using Firefox, click on the 'View Batch Edits' button. + 3. Note that the times dispayed are formatted as raw + database timestamps + 4. Note that the summary for the user bucket displays the + create time as a raw database timestamp. + 5. Navigate to a record bucket and note that its create + time is displayed as a raw timestamp as well. + 3. Apply patch. + 4. Repeat steps 2-5; this time, the times should be displayed + using the correct date and time format. + + Signed-off-by: Galen Charlton + Signed-off-by: Garry Collum + Signed-off-by: Galen Charlton + +1 1 Open-ILS/src/templates/staff/cat/bucket/share/t_bucket_info.tt2 +1 1 Open-ILS/src/templates/staff/circ/patron/bucket/t_bucket_info.tt2 +2 2 Open-ILS/src/templates/staff/circ/patron/bucket/t_changesets.tt2 + +commit 3ec4a636f7b155583fbe2aa66c45faa0ae2a665e +Author: Garry Collum +Date: Thu Jun 21 19:41:48 2018 -0400 + + LP#1778083 Location, Floating, and Age Protect missing from Items Out + + Adds columns for Location (Copy), Floating Group, and Age-based Hold + Protection to the items out grid. + + To test. + 1. View an items out screen to see that the Location, Floating Group, + and Age-based Hold protection columns are not available as options. + 2. Apply the patch. + 3. Edit some items and add definitions for Floating Group, and + Age-based hold protection. + 4. Check out these items and other items that do not have a floating + group or age-based protection. + 5. Display the Location, Floating Group, and Age-based Hold Protection + columns. + + Signed-off-by: Garry Collum + Signed-off-by: Dawn Dale + Signed-off-by: Galen Charlton + +3 0 Open-ILS/src/templates/staff/circ/patron/t_items_out.tt2 +1 1 Open-ILS/web/js/ui/default/staff/circ/patron/items_out.js + +commit c80964875a44831627621cd9c93f656ad35283fb +Author: Galen Charlton +Date: Fri Oct 5 16:41:04 2018 -0400 + + LP#1770246: (follow-up) display the open-in-new-window/tab icon + + Since the title links added by the previous patch intentionally open + the record in a new tab, display the corresponding icon to be + consistent with other interfaces. + + Signed-off-by: Galen Charlton + +1 1 Open-ILS/src/templates/staff/cat/bucket/record/t_pending.tt2 +1 1 Open-ILS/src/templates/staff/cat/bucket/record/t_search.tt2 + +commit 0ba4beb132af8b111dc60c84601f9fe4ef58df0f +Author: Garry Collum +Date: Thu May 31 21:22:35 2018 -0400 + + LP#1770246 Catalog linked title column in query and pending buckets + + To mirror the Record Bucket View grid, this patch adds a title column + in the query and pending bucket tabs that links to the catalog record + of the title displayed. The catalog record is opened in a new tab, so + the query and pending data is not lost. + + Signed-off-by: Garry Collum + Signed-off-by: Jane Sandberg + Signed-off-by: Galen Charlton + +5 0 Open-ILS/src/templates/staff/cat/bucket/record/t_pending.tt2 +5 0 Open-ILS/src/templates/staff/cat/bucket/record/t_search.tt2 + +commit 3fa6a949377be0147a6e36134595b04d39d3dfe4 +Author: Jane Sandberg +Date: Thu Oct 4 11:53:59 2018 -0700 + + Docs: adding basic info about printing spine labels + + Signed-off-by: Jane Sandberg + +17 0 docs/admin/turn-off-print-headers-chrome.adoc +31 0 docs/admin/turn-off-print-headers-firefox.adoc +4 0 docs/admin/web-client-browser-best-practices.adoc +29 0 docs/cataloging/item_status.adoc + create mode 100644 docs/admin/turn-off-print-headers-chrome.adoc + create mode 100644 docs/admin/turn-off-print-headers-firefox.adoc + +commit 6196f4f1fa6b5e5f00f0a9330c5e341f53cd5cba +Author: Jane Sandberg +Date: Mon Oct 1 19:48:32 2018 -0700 + + Docs: Adding info about copy number + + Signed-off-by: Jane Sandberg + +9 0 docs/cataloging/volcopy_editor.adoc + +commit 2a62c27a4b5df529eb4e4a1a266591f8318af0e4 +Author: Jane Sandberg +Date: Wed Sep 26 16:21:07 2018 -0700 + + Docs: adding another fix to the 3.1.6 release notes + + Signed-off-by: Jane Sandberg + +1 0 docs/RELEASE_NOTES_3_1.adoc + +commit 4ff8b3c568371504dc738ea21ae4bf1b3526c527 +Author: Jane Sandberg +Date: Wed Sep 26 16:20:05 2018 -0700 + + Docs: adding another fix to the 3.0.12 release notes + + Signed-off-by: Jane Sandberg + +1 0 docs/RELEASE_NOTES_3_0.adoc + +commit b07a601476a283492d5974c93bf29d641e42c3a0 +Author: Jane Sandberg +Date: Wed Sep 26 09:10:22 2018 -0700 + + Docs: Adding 3.1.6 release notes + + Signed-off-by: Jane Sandberg + +62 0 docs/RELEASE_NOTES_3_1.adoc + +commit 37b564f29f7c45a001e4bfa6041e1d4b303131d1 +Author: Jane Sandberg +Date: Wed Sep 26 09:05:54 2018 -0700 + + Docs: Adding release notes for 3.0.12 + + Signed-off-by: Jane Sandberg + +59 0 docs/RELEASE_NOTES_3_0.adoc diff --git a/Open-ILS/src/perlmods/lib/OpenILS/Application.pm b/Open-ILS/src/perlmods/lib/OpenILS/Application.pm index d750216454..9135221946 100644 --- a/Open-ILS/src/perlmods/lib/OpenILS/Application.pm +++ b/Open-ILS/src/perlmods/lib/OpenILS/Application.pm @@ -7,7 +7,7 @@ use OpenILS::Utils::Fieldmapper; sub ils_version { # version format is "x-y-z", for example "2-0-0" for Evergreen 2.0.0 # For branches, format is "x-y" - return "HEAD"; + return "3-2-1"; } __PACKAGE__->register_method( diff --git a/Open-ILS/src/sql/Pg/002.schema.config.sql b/Open-ILS/src/sql/Pg/002.schema.config.sql index 2aade1c737..32cd4b442d 100644 --- a/Open-ILS/src/sql/Pg/002.schema.config.sql +++ b/Open-ILS/src/sql/Pg/002.schema.config.sql @@ -93,6 +93,7 @@ CREATE TRIGGER no_overlapping_deps FOR EACH ROW EXECUTE PROCEDURE evergreen.array_overlap_check ('deprecates'); INSERT INTO config.upgrade_log (version, applied_to) VALUES ('1133', :eg_version); -- berick/kmlussier +INSERT INTO config.upgrade_log (version, applied_to) VALUES ('3.2.1', :eg_version); CREATE TABLE config.bib_source ( id SERIAL PRIMARY KEY, diff --git a/Open-ILS/src/sql/Pg/version-upgrade/3.2.0-3.2.1-upgrade-db.sql b/Open-ILS/src/sql/Pg/version-upgrade/3.2.0-3.2.1-upgrade-db.sql new file mode 100644 index 0000000000..c341a6bd29 --- /dev/null +++ b/Open-ILS/src/sql/Pg/version-upgrade/3.2.0-3.2.1-upgrade-db.sql @@ -0,0 +1,5 @@ +--Upgrade Script for 3.2.0 to 3.2.1 +\set eg_version '''3.2.1''' +BEGIN; +INSERT INTO config.upgrade_log (version, applied_to) VALUES ('3.2.1', :eg_version); +COMMIT; diff --git a/Open-ILS/xul/staff_client/chrome/content/main/about.html b/Open-ILS/xul/staff_client/chrome/content/main/about.html index b2b87b683f..b761667b24 100644 --- a/Open-ILS/xul/staff_client/chrome/content/main/about.html +++ b/Open-ILS/xul/staff_client/chrome/content/main/about.html @@ -1,7 +1,7 @@

Evergreen

Target Server ID:

-

$HeadURL$

+

http://git.evergreen-ils.org/?p=Evergreen.git;a=shortlog;h=refs/heads/tags/rel_3_2_1

What is Evergreen?

diff --git a/Open-ILS/xul/staff_client/defaults/preferences/prefs.js b/Open-ILS/xul/staff_client/defaults/preferences/prefs.js index 0613a13ddf..1a185c5f14 100644 --- a/Open-ILS/xul/staff_client/defaults/preferences/prefs.js +++ b/Open-ILS/xul/staff_client/defaults/preferences/prefs.js @@ -11,7 +11,7 @@ pref("toolkit.singletonWindowType", "eg_main"); pref("open-ils.enable_join_tabs", true); // We'll use this one to help brand some build information into the client, and rely on subversion keywords -pref("open-ils.repository.headURL","$HeadURL$"); +pref("open-ils.repository.headURL","http://git.evergreen-ils.org/?p=Evergreen.git;a=shortlog;h=refs/heads/tags/rel_3_2_1"); pref("open-ils.repository.author","$Author$"); pref("open-ils.repository.revision","$Revision$"); pref("open-ils.repository.date","$Date$"); diff --git a/Open-ILS/xul/staff_client/windowssetup.nsi b/Open-ILS/xul/staff_client/windowssetup.nsi index a9543579a8..ed4c4febe1 100644 --- a/Open-ILS/xul/staff_client/windowssetup.nsi +++ b/Open-ILS/xul/staff_client/windowssetup.nsi @@ -3,7 +3,7 @@ ; HM NIS Edit Wizard helper defines ; Old versions of makensis don't like this, moved to Makefile ;!define /file PRODUCT_VERSION "client/VERSION" -!define PRODUCT_TAG "Master" +!define PRODUCT_TAG "3.2" !define PRODUCT_INSTALL_TAG "${PRODUCT_TAG}" !define UI_IMAGESET "beta" ;!define UI_IMAGESET "release" diff --git a/README b/README deleted file mode 120000 index 1ee2103e6f..0000000000 --- a/README +++ /dev/null @@ -1 +0,0 @@ -docs/installation/server_installation.adoc \ No newline at end of file diff --git a/README b/README new file mode 100644 index 0000000000..8b81d350f1 --- /dev/null +++ b/README @@ -0,0 +1,647 @@ +Installing the Evergreen server +=============================== +:toc: +:numbered: + +Preamble: referenced user accounts +---------------------------------- + +In subsequent sections, we will refer to a number of different accounts, as +follows: + + * Linux user accounts: + ** The *user* Linux account is the account that you use to log onto the + Linux system as a regular user. + ** The *root* Linux account is an account that has system administrator + privileges. On Debian you can switch to this account from + your *user* account by issuing the `su -` command and entering the + password for the *root* account when prompted. On Ubuntu you can switch + to this account from your *user* account using the `sudo su -` command + and entering the password for your *user* account when prompted. + ** The *opensrf* Linux account is an account that you create when installing + OpenSRF. You can switch to this account from the *root* account by + issuing the `su - opensrf` command. + ** The *postgres* Linux account is created automatically when you install + the PostgreSQL database server. You can switch to this account from the + *root* account by issuing the `su - postgres` command. + * PostgreSQL user accounts: + ** The *evergreen* PostgreSQL account is a superuser account that you will + create to connect to the PostgreSQL database server. + * Evergreen administrator account: + ** The *egadmin* Evergreen account is an administrator account for + Evergreen that you will use to test connectivity and configure your + Evergreen instance. + +Preamble: developer instructions +-------------------------------- + +[NOTE] +Skip this section if you are using an official release tarball downloaded +from http://evergreen-ils.org/egdownloads + +Developers working directly with the source code from the Git repository, +rather than an official release tarball, must perform one step before they +can proceed with the `./configure` step. + +As the *user* Linux account, issue the following command in the Evergreen +source directory to generate the configure script and Makefiles: + +[source, bash] +------------------------------------------------------------------------------ +autoreconf -i +------------------------------------------------------------------------------ + +Installing prerequisites +------------------------ + + * **PostgreSQL**: The minimum supported version is 9.4. + * **Linux**: Evergreen has been tested on Debian Stretch (9), + Debian Jessie (8), Ubuntu Xenial Xerus (16.04), and Ubuntu + Trusty Tahr (14.04). + If you are running an older version of these distributions, you may want + to upgrade before upgrading Evergreen. For instructions on upgrading these + distributions, visit the Debian or Ubuntu websites. + * **OpenSRF**: The minimum supported version of OpenSRF is 3.0.0. + + +Evergreen has a number of prerequisite packages that must be installed +before you can successfully configure, compile, and install Evergreen. + +1. Begin by installing the most recent version of OpenSRF (3.0.0 or later). + You can download OpenSRF releases from http://evergreen-ils.org/opensrf-downloads/ +2. On some distributions, it is necessary to install PostgreSQL 9.4+ from external + repositories. ++ + * Ubuntu (Trusty) comes with an older version of PostgreSQL, so + steps are taken to automatically utilize the PostgreSQL + community's apt sources. + (For complete details, see: https://wiki.postgresql.org/wiki/Apt) + * Debian (Jessie/Stretch) and Ubuntu (Xenial) comes with PostgreSQL 9.4+, + so no additional steps are required. ++ +3. Issue the following commands as the *root* Linux account to install + prerequisites using the `Makefile.install` prerequisite installer, + substituting `debian-stretch`, `debian-jessie`,`ubuntu-xenial`, + or `ubuntu-trusty` for below: ++ +[source, bash] +------------------------------------------------------------------------------ +make -f Open-ILS/src/extras/Makefile.install +------------------------------------------------------------------------------ ++ +4. OPTIONAL: Developer additions ++ +To perform certain developer tasks from a Git source code checkout, +additional packages may be required. As the *root* Linux account: ++ + * To install packages needed for retrieving and managing web dependencies, + use the -developer Makefile.install target. Currently, + this is only needed for building and installing the web + staff client. ++ +[source, bash] +------------------------------------------------------------------------------ +make -f Open-ILS/src/extras/Makefile.install -developer +------------------------------------------------------------------------------ ++ + * To install packages required for building Evergreen translations, use + the -translator Makefile.install target. ++ +[source, bash] +------------------------------------------------------------------------------ +make -f Open-ILS/src/extras/Makefile.install -translator +------------------------------------------------------------------------------ ++ + * To install packages required for building Evergreen release bundles, use + the -packager Makefile.install target. ++ +[source, bash] +------------------------------------------------------------------------------ +make -f Open-ILS/src/extras/Makefile.install -packager +------------------------------------------------------------------------------ + +Extra steps for web staff client +-------------------------------- + +[NOTE] +Skip this entire section if you are using an official release tarball downloaded +from http://evergreen-ils.org/downloads + +Install dependencies for web staff client +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +[NOTE] +You may skip this section if you have installed the +<>. You will still need to do the following +steps in <>. + +1. Install the long-term stability (LTS) release of +https://nodejs.org[Node.js]. Add the Node.js `/bin` directory to your +environment variable `PATH`. + +[[install_files_for_web_staff_client]] +Install AngularJS files for web staff client +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +1. Building, Testing, Minification: The remaining steps all take place within + the staff JS web root: ++ +[source,sh] +------------------------------------------------------------------------------ +cd $EVERGREEN_ROOT/Open-ILS/web/js/ui/default/staff/ +------------------------------------------------------------------------------ ++ +2. Install Project-local Dependencies. npm inspects the 'package.json' file + for dependencies and fetches them from the Node package network. ++ +[source,sh] +------------------------------------------------------------------------------ +npm install # fetch JS dependencies +------------------------------------------------------------------------------ ++ +3. Run the build script. ++ +[source,sh] +------------------------------------------------------------------------------ +# build, run tests, concat+minify +npm run build-prod +npm run test +------------------------------------------------------------------------------ + +[[install_files_for_angular_web_staff_client]] +Install Angular files for web staff client +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +1. Building, Testing, Minification: The remaining steps all take place within + the Angular staff root: ++ +[source,sh] +------------------------------------------------------------------------------ +cd $EVERGREEN_ROOT/Open-ILS/src/eg2/ +------------------------------------------------------------------------------ ++ +2. Install Project-local Dependencies. npm inspects the 'package.json' file + for dependencies and fetches them from the Node package network. ++ +[source,sh] +------------------------------------------------------------------------------ +npm install # fetch JS dependencies +------------------------------------------------------------------------------ ++ +3. Run the build script. ++ +[source,sh] +------------------------------------------------------------------------------ +# build and run tests +ng build --prod +npm run test +------------------------------------------------------------------------------ + +Configuration and compilation instructions +------------------------------------------ + +For the time being, we are still installing everything in the `/openils/` +directory. From the Evergreen source directory, issue the following commands as +the *user* Linux account to configure and build Evergreen: + +[source, bash] +------------------------------------------------------------------------------ +PATH=/openils/bin:$PATH ./configure --prefix=/openils --sysconfdir=/openils/conf +make +------------------------------------------------------------------------------ + +These instructions assume that you have also installed OpenSRF under `/openils/`. +If not, please adjust PATH as needed so that the Evergreen `configure` script +can find `osrf_config`. + +Installation instructions +------------------------- + +1. Once you have configured and compiled Evergreen, issue the following + command as the *root* Linux account to install Evergreen and copy + example configuration files to `/openils/conf`. ++ +[source, bash] +------------------------------------------------------------------------------ +make install +------------------------------------------------------------------------------ + +Change ownership of the Evergreen files +--------------------------------------- + +All files in the `/openils/` directory and subdirectories must be owned by the +`opensrf` user. Issue the following command as the *root* Linux account to +change the ownership on the files: + +[source, bash] +------------------------------------------------------------------------------ +chown -R opensrf:opensrf /openils +------------------------------------------------------------------------------ + +Run ldconfig +------------ + +On Debian Stretch, run the following command as the root user: + +[source, bash] +------------------------------------------------------------------------------ +ldconfig +------------------------------------------------------------------------------ + +Additional Instructions for Developers +-------------------------------------- + +[NOTE] +Skip this section if you are using an official release tarball downloaded +from http://evergreen-ils.org/egdownloads + +Developers working directly with the source code from the Git repository, +rather than an official release tarball, need to install the Dojo Toolkit +set of JavaScript libraries. The appropriate version of Dojo is included in +Evergreen release tarballs. Developers should install the Dojo 1.3.3 version +of Dojo by issuing the following commands as the *opensrf* Linux account: + +[source, bash] +------------------------------------------------------------------------------ +wget http://download.dojotoolkit.org/release-1.3.3/dojo-release-1.3.3.tar.gz +tar -C /openils/var/web/js -xzf dojo-release-1.3.3.tar.gz +cp -r /openils/var/web/js/dojo-release-1.3.3/* /openils/var/web/js/dojo/. +------------------------------------------------------------------------------ + + +Configure the Apache Web server +------------------------------- + +. Use the example configuration files to configure your Web server for +the Evergreen catalog, web staff client, Web services, and administration +interfaces. Issue the following commands as the *root* Linux account: ++ +[source,bash] +------------------------------------------------------------------------------------ +cp Open-ILS/examples/apache_24/eg_24.conf /etc/apache2/sites-available/eg.conf +cp Open-ILS/examples/apache_24/eg_vhost_24.conf /etc/apache2/eg_vhost.conf +cp Open-ILS/examples/apache_24/eg_startup /etc/apache2/ +# Now set up SSL +mkdir /etc/apache2/ssl +cd /etc/apache2/ssl +------------------------------------------------------------------------------------ ++ +. The `openssl` command cuts a new SSL key for your Apache server. For a +production server, you should purchase a signed SSL certificate, but you can +just use a self-signed certificate and accept the warnings in the +and browser during testing and development. Create an SSL key for the Apache +server by issuing the following command as the *root* Linux account: ++ +[source,bash] +------------------------------------------------------------------------------ +openssl req -new -x509 -days 365 -nodes -out server.crt -keyout server.key +------------------------------------------------------------------------------ ++ +. As the *root* Linux account, edit the `eg.conf` file that you copied into +place. + a. To enable access to the offline upload / execute interface from any + workstation on any network, make the following change (and note that + you *must* secure this for a production instance): + * Replace `Require host 10.0.0.0/8` with `Require all granted` +. Change the user for the Apache server. + * As the *root* Linux account, edit + `/etc/apache2/envvars`. Change `export APACHE_RUN_USER=www-data` to + `export APACHE_RUN_USER=opensrf`. +. As the *root* Linux account, configure Apache with KeepAlive settings + appropriate for Evergreen. Higher values can improve the performance of a + single client by allowing multiple requests to be sent over the same TCP + connection, but increase the risk of using up all available Apache child + processes and memory. + * Edit `/etc/apache2/apache2.conf`. + a. Change `KeepAliveTimeout` to `1`. + b. Change `MaxKeepAliveRequests` to `100`. +. As the *root* Linux account, configure the prefork module to start and keep + enough Apache servers available to provide quick responses to clients without + running out of memory. The following settings are a good starting point for a + site that exposes the default Evergreen catalogue to the web: ++ +.`/etc/apache2/mods-available/mpm_prefork.conf` +[source,bash] +------------------------------------------------------------------------------ + + StartServers 15 + MinSpareServers 5 + MaxSpareServers 15 + MaxRequestWorkers 75 + MaxConnectionsPerChild 500 + +------------------------------------------------------------------------------ ++ +. As the *root* user, enable the mpm_prefork module: ++ +[source,bash] +------------------------------------------------------------------------------ +a2dismod mpm_event +a2enmod mpm_prefork +------------------------------------------------------------------------------ ++ +. As the *root* Linux account, enable the Evergreen site: ++ +[source,bash] +------------------------------------------------------------------------------ +a2dissite 000-default # OPTIONAL: disable the default site (the "It Works" page) +a2ensite eg.conf +------------------------------------------------------------------------------ ++ +. As the *root* Linux account, enable Apache to write + to the lock directory; this is currently necessary because Apache + is running as the `opensrf` user: ++ +[source,bash] +------------------------------------------------------------------------------ +chown opensrf /var/lock/apache2 +------------------------------------------------------------------------------ + +Learn more about additional Apache options in the following sections: + + * <<_apache_rewrite_tricks,Apache Rewrite Tricks>> + * <<_apache_access_handler_perl_module,Apache Access Handler Perl Module>> + +Configure OpenSRF for the Evergreen application +----------------------------------------------- +There are a number of example OpenSRF configuration files in `/openils/conf/` +that you can use as a template for your Evergreen installation. Issue the +following commands as the *opensrf* Linux account: + +[source, bash] +------------------------------------------------------------------------------ +cp -b /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml +cp -b /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml +------------------------------------------------------------------------------ + +When you installed OpenSRF, you created four Jabber users on two +separate domains and edited the `opensrf_core.xml` file accordingly. Please +refer back to the OpenSRF README and, as the *opensrf* Linux account, edit the +Evergreen version of the `opensrf_core.xml` file using the same Jabber users +and domains as you used while installing and testing OpenSRF. + +[NOTE] +The `-b` flag tells the `cp` command to create a backup version of the +destination file. The backup version of the destination file has a tilde (`~`) +appended to the file name, so if you have forgotten the Jabber users and +domains, you can retrieve the settings from the backup version of the files. + +`eg_db_config`, described in <<_creating_the_evergreen_database,Creating the Evergreen +database>>, sets the database connection information in `opensrf.xml` for you. + +Configure action triggers for the Evergreen application +------------------------------------------------------- +_Action Triggers_ provide hooks for the system to perform actions when a given +event occurs; for example, to generate reminder or overdue notices, the +`checkout.due` hook is processed and events are triggered for potential actions +if there is no checkin time. + +To enable the default set of hooks, issue the following command as the +*opensrf* Linux account: + +[source, bash] +------------------------------------------------------------------------------ +cp -b /openils/conf/action_trigger_filters.json.example /openils/conf/action_trigger_filters.json +------------------------------------------------------------------------------ + +For more information about configuring and running action triggers, see +<<_processing_action_triggers,Notifications / Action Triggers>>. + +Creating the Evergreen database +------------------------------- + +Setting up the PostgreSQL server +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +For production use, most libraries install the PostgreSQL database server on a +dedicated machine. Therefore, by default, the `Makefile.install` prerequisite +installer does *not* install the PostgreSQL 9 database server that is required +by every Evergreen system. You can install the packages required by Debian or +Ubuntu on the machine of your choice using the following commands as the +*root* Linux account: + +. Installing PostgreSQL server packages + +Each OS build target provides the postgres server installation packages +required for each operating system. To install Postgres server packages, +use the make target 'postgres-server-'. Choose the most appropriate +command below based on your operating system. + +[source, bash] +------------------------------------------------------------------------------ +make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-stretch +make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-jessie +make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-trusty +make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-xenial +------------------------------------------------------------------------------ + +For a standalone PostgreSQL server, install the following Perl modules for your +distribution as the *root* Linux account: + +.(Debian and Ubuntu) +No extra modules required for these distributions. + +You need to create a PostgreSQL superuser to create and access the database. +Issue the following command as the *postgres* Linux account to create a new +PostgreSQL superuser named `evergreen`. When prompted, enter the new user's +password: + +[source, bash] +------------------------------------------------------------------------------ +createuser -s -P evergreen +------------------------------------------------------------------------------ + +.Enabling connections to the PostgreSQL database + +Your PostgreSQL database may be configured by default to prevent connections, +for example, it might reject attempts to connect via TCP/IP or from other +servers. To enable TCP/IP connections from localhost, check your `pg_hba.conf` +file, found in the `/etc/postgresql/` directory on Debian and Ubuntu. +A simple way to enable TCP/IP +connections from localhost to all databases with password authentication, which +would be suitable for a test install of Evergreen on a single server, is to +ensure the file contains the following entries _before_ any "host ... ident" +entries: + +------------------------------------------------------------------------------ +host all all ::1/128 md5 +host all all 127.0.0.1/32 md5 +------------------------------------------------------------------------------ + +When you change the `pg_hba.conf` file, you will need to reload PostgreSQL to +make the changes take effect. For more information on configuring connectivity +to PostgreSQL, see +http://www.postgresql.org/docs/devel/static/auth-pg-hba-conf.html + +Creating the Evergreen database and schema +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Once you have created the *evergreen* PostgreSQL account, you also need to +create the database and schema, and configure your configuration files to point +at the database server. Issue the following command as the *root* Linux account +from inside the Evergreen source directory, replacing , , +, , and with the appropriate values for your +PostgreSQL database (where and are for the *evergreen* +PostgreSQL account you just created), and replace and +with the values you want for the *egadmin* Evergreen administrator account: + +[source, bash] +------------------------------------------------------------------------------ +perl Open-ILS/src/support-scripts/eg_db_config --update-config \ + --service all --create-database --create-schema --create-offline \ + --user --password --hostname --port \ + --database --admin-user --admin-pass +------------------------------------------------------------------------------ + +This creates the database and schema and configures all of the services in +your `/openils/conf/opensrf.xml` configuration file to point to that database. +It also creates the configuration files required by the Evergreen `cgi-bin` +administration scripts, and sets the user name and password for the *egadmin* +Evergreen administrator account to your requested values. + +You can get a complete set of options for `eg_db_config` by passing the +`--help` parameter. + +Loading sample data +~~~~~~~~~~~~~~~~~~~ +If you add the `--load-all-sample` parameter to the `eg_db_config` command, +a set of authority and bibliographic records, call numbers, copies, staff +and regular users, and transactions will be loaded into your target +database. This sample dataset is commonly referred to as the _concerto_ +sample data, and can be useful for testing out Evergreen functionality and +for creating problem reports that developers can easily recreate with their +own copy of the _concerto_ sample data. + +Creating the database on a remote server +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +In a production instance of Evergreen, your PostgreSQL server should be +installed on a dedicated server. + +PostgreSQL 9.4 and later +^^^^^^^^^^^^^^^^^^^^^^^^ +To create the database instance on a remote database server running PostgreSQL +9.4 or later, simply use the `--create-database` flag on `eg_db_config`. + +Starting Evergreen +------------------ +1. As the *root* Linux account, start the `memcached` and `ejabberd` services +(if they aren't already running): ++ +[source, bash] +------------------------------------------------------------------------------ +/etc/init.d/ejabberd start +/etc/init.d/memcached start +------------------------------------------------------------------------------ ++ +2. As the *opensrf* Linux account, start Evergreen. The `-l` flag in the +following command is only necessary if you want to force Evergreen to treat the +hostname as `localhost`; if you configured `opensrf.xml` using the real +hostname of your machine as returned by `perl -ENet::Domain 'print +Net::Domain::hostfqdn() . "\n";'`, you should not use the `-l` flag. ++ +[source, bash] +------------------------------------------------------------------------------ +osrf_control -l --start-all +------------------------------------------------------------------------------ ++ + ** If you receive the error message `bash: osrf_control: command not found`, + then your environment variable `PATH` does not include the `/openils/bin` + directory; this should have been set in the *opensrf* Linux account's + `.bashrc` configuration file. To manually set the `PATH` variable, edit the + configuration file `~/.bashrc` as the *opensrf* Linux account and add the + following line: ++ +[source, bash] +------------------------------------------------------------------------------ +export PATH=$PATH:/openils/bin +------------------------------------------------------------------------------ ++ +3. As the *opensrf* Linux account, generate the Web files needed by the web staff + client and catalogue and update the organization unit proximity (you need to do + this the first time you start Evergreen, and after that each time you change the library org unit configuration. +): ++ +[source, bash] +------------------------------------------------------------------------------ +autogen.sh +------------------------------------------------------------------------------ ++ +4. As the *root* Linux account, restart the Apache Web server: ++ +[source, bash] +------------------------------------------------------------------------------ +/etc/init.d/apache2 restart +------------------------------------------------------------------------------ ++ +If the Apache Web server was running when you started the OpenSRF services, you +might not be able to successfully log in to the OPAC or web staff client until the +Apache Web server is restarted. + +Testing connections to Evergreen +-------------------------------- + +Once you have installed and started Evergreen, test your connection to +Evergreen via `srfsh`. As the *opensrf* Linux account, issue the following +commands to start `srfsh` and try to log onto the Evergreen server using the +*egadmin* Evergreen administrator user name and password that you set using the +`eg_db_config` command: + +[source, bash] +------------------------------------------------------------------------------ +/openils/bin/srfsh +srfsh% login +------------------------------------------------------------------------------ + +You should see a result like: + + Received Data: "250bf1518c7527a03249858687714376" + ------------------------------------ + Request Completed Successfully + Request Time in seconds: 0.045286 + ------------------------------------ + + Received Data: { + "ilsevent":0, + "textcode":"SUCCESS", + "desc":" ", + "pid":21616, + "stacktrace":"oils_auth.c:304", + "payload":{ + "authtoken":"e5f9827cc0f93b503a1cc66bee6bdd1a", + "authtime":420 + } + + } + + ------------------------------------ + Request Completed Successfully + Request Time in seconds: 1.336568 + ------------------------------------ +[[install-troubleshooting-1]] +If this does not work, it's time to do some troubleshooting. + + * As the *opensrf* Linux account, run the `settings-tester.pl` script to see + if it finds any system configuration problems. The script is found at + `Open-ILS/src/support-scripts/settings-tester.pl` in the Evergreen source + tree. + * Follow the steps in the http://evergreen-ils.org/dokuwiki/doku.php?id=troubleshooting:checking_for_errors[troubleshooting guide]. + * If you have faithfully followed the entire set of installation steps + listed here, you are probably extremely close to a working system. + Gather your configuration files and log files and contact the + http://evergreen-ils.org/communicate/mailing-lists/[Evergreen development +mailing list] for assistance before making any drastic changes to your system + configuration. + +Getting help +------------ + +Need help installing or using Evergreen? Join the mailing lists at +http://evergreen-ils.org/communicate/mailing-lists/ or contact us on the Freenode +IRC network on the #evergreen channel. + +License +------- +This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 +Unported License. To view a copy of this license, visit +http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative +Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. diff --git a/configure.ac b/configure.ac index dacb5a36b7..e2079fc4c2 100644 --- a/configure.ac +++ b/configure.ac @@ -20,8 +20,8 @@ export PATH=${PATH}:/usr/sbin AC_PREREQ(2.61) -AC_INIT(Open-ILS, trunk, open-ils-dev@list.georgialibraries.org) -AM_INIT_AUTOMAKE([OpenILS], [trunk]) +AC_INIT(Open-ILS, 3.2.1, open-ils-dev@list.georgialibraries.org) +AM_INIT_AUTOMAKE([OpenILS], [3.2.1]) AC_REVISION($Revision: 0.1 $) AC_CONFIG_SRCDIR([configure.ac]) AC_CONFIG_SUBDIRS([Open-ILS/xul/staff_client/external/libmar])