-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 59973154f825cf7881b9d781fe1320a50100d50f
+Author: Dan Wells <dbw2@calvin.edu>
+Date: Mon Feb 24 12:09:57 2014 -0500
+
+ Bump OpenILS.pm version
+
+ Signed-off-by: Dan Wells <dbw2@calvin.edu>
+
+1 1 Open-ILS/src/perlmods/lib/OpenILS.pm
+
+commit 8408675d1f473027cb7b0766700396f5b1e6010d
+Author: Dan Wells <dbw2@calvin.edu>
+Date: Wed Oct 18 17:42:05 2017 -0400
+
+ Fix stray beta1 in 3.0.0 upgrade script
+
+ I do not think this actually affects anything.
+
+ We'll fix this for early adopters in the 3.0.1 upgrade script, I
+ think.
+
+ Signed-off-by: Dan Wells <dbw2@calvin.edu>
+
+1 1 Open-ILS/src/sql/Pg/version-upgrade/2.12.6-3.0.0-upgrade-db.sql
+
+commit 251d80839f2951285d51360ee2594957a6ad1a1c
+Author: Kathy Lussier <klussier@masslnc.org>
+Date: Wed Oct 18 13:07:34 2017 -0400
+
+ Docs: 3.0.1 Release notes
+
+ Signed-off-by: Kathy Lussier <klussier@masslnc.org>
+
+63 4 docs/RELEASE_NOTES_3_0.adoc
+
+commit f8ca464030075d7a5e4dc1808df15d910573331e
+Author: Kathy Lussier <klussier@masslnc.org>
+Date: Wed Oct 18 11:58:24 2017 -0400
+
+ Docs: 2.12.7 release notes
+
+ Signed-off-by: Kathy Lussier <klussier@masslnc.org>
+
+38 0 docs/RELEASE_NOTES_2_12.adoc
+
+commit a0f458db871aba9c7545e6cb7abab6c26754f2fa
+Author: Kyle Huckins <khuckins@catalyte.io>
+Date: Fri Sep 15 21:06:24 2017 +0000
+
+ LP#1659181 Mark Items Damaged Prompt
+
+ - Add new prompt for marking an item as damaged.
+ - If there is a fee when marking an item as damaged, offer the
+ option to charge as normal, manually bill the patron, or to waive
+ the charge.
+ -Affected interfaces: Holds pull list, Holds Shelf, Patron Holds,
+ Record Holds, Record Holdings, Item Status(List), Item Status(Detail)
+
+ Signed-off-by: Kyle Huckins <khuckins@catalyte.io>
+
+ Changes to be committed:
+ modified: Open-ILS/src/perlmods/lib/OpenILS/Application/Circ.pm
+ modified: Open-ILS/src/templates/staff/cat/catalog/index.tt2
+ modified: Open-ILS/src/templates/staff/circ/checkin/index.tt2
+ modified: Open-ILS/src/templates/staff/circ/holds/index.tt2
+ new file: Open-ILS/src/templates/staff/circ/share/t_mark_damaged.tt2
+ modified: Open-ILS/web/js/ui/default/staff/cat/catalog/app.js
+ modified: Open-ILS/web/js/ui/default/staff/cat/item/app.js
+ modified: Open-ILS/web/js/ui/default/staff/circ/checkin/app.js
+ modified: Open-ILS/web/js/ui/default/staff/circ/services/circ.js
+ modified: Open-ILS/web/js/ui/default/staff/circ/services/holds.js
+ modified: Open-ILS/web/js/ui/default/staff/circ/services/item.js
+
+ Signed-off-by: Kathy Lussier <klussier@masslnc.org>
+
+32 4 Open-ILS/src/perlmods/lib/OpenILS/Application/Circ.pm
+1 0 Open-ILS/src/templates/staff/cat/catalog/index.tt2
+1 0 Open-ILS/src/templates/staff/circ/checkin/index.tt2
+1 0 Open-ILS/src/templates/staff/circ/holds/index.tt2
+53 0 Open-ILS/src/templates/staff/circ/share/t_mark_damaged.tt2
+12 3 Open-ILS/web/js/ui/default/staff/cat/catalog/app.js
+2 1 Open-ILS/web/js/ui/default/staff/cat/item/app.js
+7 6 Open-ILS/web/js/ui/default/staff/circ/checkin/app.js
+72 24 Open-ILS/web/js/ui/default/staff/circ/services/circ.js
+8 5 Open-ILS/web/js/ui/default/staff/circ/services/holds.js
+8 2 Open-ILS/web/js/ui/default/staff/circ/services/item.js
+ create mode 100644 Open-ILS/src/templates/staff/circ/share/t_mark_damaged.tt2
+
+commit 7273c8d37b78c0b17f4772e254cf6bbefc55c1d2
+Author: Jeanette Lundgren <jlundgren@cwmars.org>
+Date: Wed Oct 18 09:58:55 2017 -0400
+
+ DOCS: added tip for patron insensitive search (ignores punctuation)
+
+ Signed-off-by: Jeanette Lundgren <jlundgren@cwmars.org>
+
+1 0 docs/circulation/circulation_patron_records_web_client.adoc
+
+commit 189ba25fb03c5ee8a50182fbe286cad5c0f02c70
+Author: Cesar Velez <cesar.velez@equinoxinitiative.org>
+Date: Wed Oct 4 14:01:25 2017 -0400
+
+ LP#1712686 - display completed barcode on copy grids not partial input
+
+ The check in, check out, and renew interfaces were not displaying
+ the actual complete(d) barcode when barcode completion is on.
+ This saves the inputted partial barcode in row_item.input_barcode
+ and let's the returned acp.barcode be in row_item.copy_barcode for
+ display.
+
+ Signed-off by: Cesar Velez <cesar.velez@equinoxinitiative.org>
+
+ Signed-off-by: Mike Rylander <mrylander@gmail.com>
+
+4 2 Open-ILS/web/js/ui/default/staff/circ/checkin/app.js
+4 1 Open-ILS/web/js/ui/default/staff/circ/patron/checkout.js
+3 1 Open-ILS/web/js/ui/default/staff/circ/renew/app.js
+
+commit 240e34b1e964964525bc03c8571d7a0d00ccfad9
+Author: Cesar Velez <cesar.velez@equinoxinitiative.org>
+Date: Thu Sep 28 13:08:48 2017 -0400
+
+ LP#1714060 - fixes thinko when obeying patron.password.use_phone setting in patron regctl
+
+ There was a bug, an undefined variable was being used to assign the last
+ four digits of the day_phone to usr.passwd when this library setting
+ was being used.
+
+ Signed-off by: Cesar Velez <cesar.velez@equinoxinitiative.org>
+
+ Signed-off-by: Mike Rylander <mrylander@gmail.com>
+
+1 1 Open-ILS/web/js/ui/default/staff/circ/patron/regctl.js
+
+commit bf110600bf0ebec99ef108ff0effd003c7fb607e
+Author: Cesar Velez <cesar.velez@equinoxinitiative.org>
+Date: Wed Oct 4 10:49:02 2017 -0400
+
+ LP#1714056 - fix for webstaff patron registration not requiring DOB
+
+ For some reason the ng-required attribute was not on the dob input
+ control. Setting 'ui.patron.edit.au.dob.require' should now work
+ as intended.
+
+ Signed-off by: Cesar Velez <cesar.velez@equinoxinitiative.org>
+
+ Signed-off-by: Mike Rylander <mrylander@gmail.com>
+
+2 1 Open-ILS/src/templates/staff/circ/patron/t_edit.tt2
+
+commit 88c220cf0e26e1889257a28b34c5f75337308998
+Author: Cesar Velez <cesar.velez@equinoxinitiative.org>
+Date: Thu Oct 5 10:58:00 2017 -0400
+
+ LP#1721145 - fix Patron Message tab grids missing persist-keys
+
+ In order to store grid column config preferences locally, a persist-key
+ attribute needs to be declared for the grid. Thus, for this UI a
+ 'circ.patron.staff_messages' and a 'circ.patron.archived_messages'
+ persist-keys were added.
+
+ Signed-off by: Cesar Velez <cesar.velez@equinoxinitiative.org>
+
+ Signed-off-by: Mike Rylander <mrylander@gmail.com>
+
+4 2 Open-ILS/src/templates/staff/circ/patron/t_messages.tt2
+
+commit e9abffb9556d33a3b6edfa300e5d4f5e2e14987c
+Author: Cesar Velez <cesar.velez@equinoxinitiative.org>
+Date: Thu Sep 21 15:58:49 2017 -0400
+
+ LP#1717025 - make Specific Due Dates Until Logout in Patron Checkout
+
+ Made a few (opinionated) changes, that try to follow some JS
+ best practices. Changed Bool flags like date_options.sticky_date
+ to has_sticky_date, which avoids confusion with the checkoutArgs
+ property of the same name, and provides a clue about it's type
+ and function. Also added semicolons to any JS statements and
+ function expressions that were missing them.
+
+ Signed-off by: Cesar Velez <cesar.velez@equinoxinitiative.org>
+
+ Signed-off-by: Mike Rylander <mrylander@gmail.com>
+
+6 6 Open-ILS/src/templates/staff/circ/patron/t_checkout.tt2
+12 12 Open-ILS/web/js/ui/default/staff/circ/patron/checkout.js
+
+commit 8f294e26ca47cae973c38f872dabbe0538e01e3f
+Author: Jason Boyer <JBoyer@library.in.gov>
+Date: Wed Sep 13 15:36:47 2017 -0500
+
+ LP1717025: Persist Specific Due Dates Until Logout
+
+ Add an option to the specific due date feature to
+ save the specified date until logout. This allows
+ all circulations from a given workstation to be due
+ on the same date.
+
+ Signed-off-by: Jason Boyer <JBoyer@library.in.gov>
+ Signed-off-by: Cesar Velez <cesar.velez@equinoxinitiative.org>
+ Signed-off-by: Mike Rylander <mrylander@gmail.com>
+
+34 6 Open-ILS/src/templates/staff/circ/patron/t_checkout.tt2
+47 0 Open-ILS/web/js/ui/default/staff/circ/patron/checkout.js
+
+commit 4eb23600cf3fb1fef7384d628a0c18702d238c47
+Author: Bill Erickson <berickxx@gmail.com>
+Date: Mon Sep 25 10:35:07 2017 -0400
+
+ LP#1717010 Webstaff print/export full grid
+
+ 1. Adds a new 'Print Full Grid' action which generates printer-friendly
+ HTML output of all grid rows. The print content matches the display
+ grid structure, uses the same field filters (e.g. for formatting dates)
+ and is retrieved using the same query and sort parameters as the display
+ grid.
+
+ To render the grid as HTML, a new print HTML template is included at
+ print_templates/t_grid_html.tt2.
+
+ 2. Modifies the 'Export CSV' action to export all grid rows instead of
+ only the visible rows. The link label is modified to 'Export Full CSV'
+ to better indicate its intent.
+
+ Signed-off-by: Bill Erickson <berickxx@gmail.com>
+ Signed-off-by: Mike Rylander <mrylander@gmail.com>
+
+26 0 Open-ILS/src/templates/staff/share/print_templates/t_grid_html.tt2
+4 4 Open-ILS/src/templates/staff/share/t_autogrid.tt2
+131 32 Open-ILS/web/js/ui/default/staff/services/grid.js
+ create mode 100644 Open-ILS/src/templates/staff/share/print_templates/t_grid_html.tt2
+
+commit 085472193502d22ff4529940bd3bfafb677aab8d
+Author: Cesar Velez <Cesar.Velez@equinoxinitiative.org>
+Date: Wed Sep 27 18:16:04 2017 +0100
+
+ LP#1716962 - honor In-House Use: num of uses threshold setting
+
+ The 'ui.circ.in_house_use.entry_warn' library setting was not being
+ taken into account nor any confirmation/warning modal being shown.
+ This fix addresses that by watching the changes and if selected
+ num_uses value exceeds setting value, displays egConfirm modal.
+
+ Signed-off by: Cesar Velez <cesar.velez@equinoxinitiative.org>
+
+ Signed-off-by: Mike Rylander <mrylander@gmail.com>
+
+1 0 Open-ILS/src/templates/staff/base_js.tt2
+1 1 Open-ILS/src/templates/staff/circ/in_house_use/index.tt2
+20 2 Open-ILS/web/js/ui/default/staff/circ/in_house_use/app.js
+
+commit bd062fad7ed8495e1a4516c7f1f3b2a090378448
+Author: Cesar Velez <cesar.velez@equinoxinitiative.org>
+Date: Thu Oct 12 17:31:37 2017 -0400
+
+ LP#1719967 - Add alert message field to volcopy editor
+
+ As 1676608 was deferred to 3.1, this adds a copy alert_message
+ field, to the volcopy editor. The defaults tab "Alerts" checkbox has
+ been replaced by "Alert Message" and this new field will be active until replaced by
+ the changes of 3.1.
+
+ Signed-off by: Cesar Velez <cesar.velez@equinoxinitiative.org>
+
+ Signed-off-by: Mike Rylander <mrylander@gmail.com>
+
+28 6 Open-ILS/src/templates/staff/cat/volcopy/t_attr_edit.tt2
+3 2 Open-ILS/src/templates/staff/cat/volcopy/t_defaults.tt2
+4 1 Open-ILS/web/js/ui/default/staff/cat/volcopy/app.js
+
+commit 30be921dbdca77c1e7ca760028ab00cd53215a69
+Author: Jane Sandberg <sandbej@linnbenton.edu>
+Date: Sun Oct 15 21:10:00 2017 -0700
+
+ Docs: adding backup information to cli manual
+
+ Signed-off-by: Jane Sandberg <sandbej@linnbenton.edu>
+
+207 0 docs/admin/backups.adoc
+58 0 docs/root.adoc
+2 0 docs/root_command_line_admin.adoc
+ create mode 100644 docs/admin/backups.adoc
+
+commit 4fd8ef78c2e151f8968b9753144fd1f59099b7dc
+Author: Jane Sandberg <sandbej@linnbenton.edu>
+Date: Sun Oct 15 10:50:42 2017 -0700
+
+ Docs: adding new services to command line manual
+
+ Signed-off-by: Jane Sandberg <sandbej@linnbenton.edu>
+
+4 0 docs/root_command_line_admin.adoc
+
+commit 7a2c29e0de700d84b7c0b722b96e35ebad0941ad
+Author: Jane Sandberg <sandbej@linnbenton.edu>
+Date: Sun Oct 15 10:47:18 2017 -0700
+
+ Docs: 2 new services
+
+ Signed-off-by: Jane Sandberg <sandbej@linnbenton.edu>
+
+12 0 docs/admin/ebook_api_service.adoc
+5 0 docs/admin/hold_targeter_service.adoc
+4 0 docs/root.adoc
+ create mode 100644 docs/admin/ebook_api_service.adoc
+ create mode 100644 docs/admin/hold_targeter_service.adoc
+
+commit d73bfa44fe3110b80ef4b2ea8aa85b0feff78583
+Author: Remington Steed <rjs7@calvin.edu>
+Date: Thu Oct 5 09:26:39 2017 -0400
+
+ LP#1721557 Fix Vandelay export within web client
+
+ Triggering a file download from dojo pages within the web client
+ requires a new technique. This commit borrows from the acq lineitem
+ table export (acq/common/li_table.js) and applies the technique to the
+ vandelay feature.
+
+ Signed-off-by: Remington Steed <rjs7@calvin.edu>
+ Signed-off-by: Cesar Velez <cesar.velez@equinoxinitiative.org>
+ Signed-off-by: Galen Charlton <gmc@equinoxinitiative.org>
+
+1 0 Open-ILS/src/templates/vandelay/vandelay.tt2
+18 7 Open-ILS/web/js/ui/default/vandelay/vandelay.js
+
+commit f2c17a558fcf6580d0a91686db9baea4decc0e2c
+Author: Jane Sandberg <sandbej@linnbenton.edu>
+Date: Wed Oct 11 07:43:05 2017 -0700
+
+ Docs: located URIs don't work with trailing spaces
+
+ Signed-off-by: Jane Sandberg <sandbej@linnbenton.edu>
+
+4 0 docs/cataloging/cataloging_electronic_resources.adoc
+
+commit ca9341eafee5983126c72f1757e13ca3cf074853
+Author: Jane Sandberg <sandbej@linnbenton.edu>
+Date: Tue Oct 10 20:11:35 2017 -0700
+
+ Docs: documentation for Record Buckets
+
+ Signed-off-by: Jane Sandberg <sandbej@linnbenton.edu>
+
+62 0 docs/cataloging/record_buckets.adoc
+4 0 docs/root.adoc
+3 0 docs/root_cataloging.adoc
+ create mode 100755 docs/cataloging/record_buckets.adoc
+
+commit 399baa3339e393ab67066458bcfbc6def7ec596d
+Author: Jane Sandberg <sandbej@linnbenton.edu>
+Date: Tue Oct 10 18:14:30 2017 -0700
+
+ Docs: updating copy buckets docs
+
+ Signed-off-by: Jane Sandberg <sandbej@linnbenton.edu>
+
+10 3 docs/cataloging/copy-buckets_web_client.adoc
+
+commit b7b1703c2f36d049701f5104d29c6a08e1b55b3d
+Author: Jane Sandberg <sandbej@linnbenton.edu>
+Date: Fri Oct 6 07:12:24 2017 -0700
+
+ Docs: bumping release notes for consolidated manual to 3.0
+
+ Signed-off-by: Jane Sandberg <sandbej@linnbenton.edu>
+
+1 1 docs/root.adoc
+
+commit 50ed4c3692e55246769735b9500e19c36fd22306
+Author: Kathy Lussier <klussier@masslnc.org>
+Date: Thu Oct 5 11:12:10 2017 -0400
+
+ Docs: remove electronic resources heading
+
+ The additional heading isn't needed in the release notes.
+
+ Signed-off-by: Kathy Lussier <klussier@masslnc.org>
+
+0 4 docs/RELEASE_NOTES_3_0.adoc
+
+commit 1417bb6b64fc6a5f51a1edff9750a5f17e80760b
+Author: Kathy Lussier <klussier@masslnc.org>
+Date: Thu Oct 5 11:04:54 2017 -0400
+
+ Docs: ebook api release note entry and doc changes
+
+ Moved the content from ebook_transactions.adoc file to the 3.0 release notes.
+ I also incorporated changes introduced in 3.0 into the documentation on
+ ebook api.
+
+ Signed-off-by: Kathy Lussier <klussier@masslnc.org>
+
+36 0 docs/RELEASE_NOTES_3_0.adoc
+18 6 docs/admin/ebook_api.adoc
+0 36 docs/opac/ebook_transactions.adoc
+ delete mode 100644 docs/opac/ebook_transactions.adoc
+
+commit 9a4cfcddc981d016b5932b748978eecb19bbb086
+Author: Kathy Lussier <klussier@masslnc.org>
+Date: Fri Sep 29 11:10:03 2017 -0400
+
+ LP#1720394: This html thinko in copy tag display
+
+ A closing td tag appears to be have been accidentally used when closing the
+ opening td tag. It doesn't appear to affect the display of the copy tag, but should probably be fixed.
+
+ Signed-off-by: Kathy Lussier <klussier@masslnc.org>
+ Signed-off-by: Galen Charlton <gmc@equinoxinitiative.org>
+
+1 1 Open-ILS/src/templates/opac/parts/record/copy_table.tt2
+
+commit de31a7149cb2338472cc0605c1c1486716ebba23
+Author: Bill Erickson <berickxx@gmail.com>
+Date: Wed Sep 27 11:30:47 2017 -0400
+
+ LP#1717007 Improve egProgressDialog collision handling
+
+ Resolves a race condition where egProgressDialog.open() is called twice
+ before the first call completes (i.e. the dialog is opened), leaving 2
+ open dialogs, one of which cannot be closed because its reference is
+ lost.
+
+ Going forward, attempts to open multiple dialogs will always result in
+ the most recently visible dialog taking preference. When collisions
+ occur, a warning is also issued to the console.
+
+ Signed-off-by: Bill Erickson <berickxx@gmail.com>
+ Signed-off-by: Cesar Velez <cesar.velez@equinoxinitiative.org>
+ Signed-off-by: Galen Charlton <gmc@equinoxinitiative.org>
+
+16 10 Open-ILS/web/js/ui/default/staff/services/ui.js
+
+commit 4a523631cd58db6b20867bc63253c52ee04cda54
+Author: Galen Charlton <gmc@equinoxinitiative.org>
+Date: Wed Oct 4 12:10:31 2017 -0400
+
+ LP#1666512: stamp DB update
+
+ Signed-off-by: Galen Charlton <gmc@equinoxinitiative.org>
+
+1 1 Open-ILS/src/sql/Pg/002.schema.config.sql
+22 0 Open-ILS/src/sql/Pg/upgrade/1078.data.add_possibly_missing_billing_types.sql
+0 22 Open-ILS/src/sql/Pg/upgrade/XXXX.data.add_possibly_missing_billing_types.sql
+ create mode 100644 Open-ILS/src/sql/Pg/upgrade/1078.data.add_possibly_missing_billing_types.sql
+ delete mode 100644 Open-ILS/src/sql/Pg/upgrade/XXXX.data.add_possibly_missing_billing_types.sql
+
+commit 32ae404b66a01f768bd16c6bb85a6a6d721f8344
+Author: Ben Shum <ben@evergreener.net>
+Date: Thu Sep 14 23:16:32 2017 -0400
+
+ LP#1666512 - Only insert if not already existing
+
+ This repatch was requested by Galen Charlton to make it easier for
+ upgrades to avoid adding the entries or failing if the entries already
+ existed.
+
+ Also drops the unnecessary i18n tagging for the billing type names
+ since it does not work with applying upgrade scripts (only for sourcing
+ db.seed data for translation to PO file)
+
+ Signed-off-by: Ben Shum <ben@evergreener.net>
+ Signed-off-by: Chris Sharp <csharp@georgialibraries.org>
+ Signed-off-by: Galen Charlton <gmc@equinoxinitiative.org>
+
+11 6 Open-ILS/src/sql/Pg/upgrade/XXXX.data.add_possibly_missing_billing_types.sql
+
+commit 78a0782928fbe561125391bd64d5ff3576c43ec1
+Author: Chris Sharp <csharp@georgialibraries.org>
+Date: Tue Feb 21 08:03:55 2017 -0500
+
+ LP#1666512 - Add billing types from 2009-era features.
+
+ For systems that were running Evergreen 1.2 or so and upgraded to 1.4
+ or so, there were billing types added that did not make it into an
+ upgrade script. We add them here just in case you don't have them.
+ Systems installed since Evergreen 1.4 are probably not affected.
+
+ Signed-off-by: Chris Sharp <csharp@georgialibraries.org>
+ Signed-off-by: Ben Shum <ben@evergreener.net>
+ Signed-off-by: Galen Charlton <gmc@equinoxinitiative.org>
+
+17 0 Open-ILS/src/sql/Pg/upgrade/XXXX.data.add_possibly_missing_billing_types.sql
+ create mode 100644 Open-ILS/src/sql/Pg/upgrade/XXXX.data.add_possibly_missing_billing_types.sql
+
+commit 6bcb34bae83eaaa638e57a8705a21dcbeca8beef
+Author: Galen Charlton <gmc@equinoxinitiative.org>
+Date: Tue Oct 3 16:50:41 2017 -0400
+
+ correct the acknowledgement of Consortium of Ohio Libraries
+
+ Signed-off-by: Galen Charlton <gmc@equinoxinitiative.org>
+
+1 1 docs/RELEASE_NOTES_3_0.adoc
--- /dev/null
+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), Debian Wheezy (7), 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.
++
+ * Debian (Wheezy) and Ubuntu (Trusty) comes with older versions 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`, `debian-wheezy`,
+ `ubuntu-xenial`, or `ubuntu-trusty` for <osname> below:
++
+[source, bash]
+------------------------------------------------------------------------------
+make -f Open-ILS/src/extras/Makefile.install <osname>
+------------------------------------------------------------------------------
++
+4. Add the libdbi-libdbd libraries to the system dynamic library path by
+ issuing the following commands as the *root* Linux account:
++
+[NOTE]
+You should skip this step if installing on Ubuntu Trusty/Xenial or Debian Jessie/Stretch. The Ubuntu
+and Debian Jessie/Stretch targets use libdbd-pgsql from packages.
++
+.Debian Wheezy
+[source, bash]
+------------------------------------------------------------------------------
+echo "/usr/local/lib/dbd" > /etc/ld.so.conf.d/eg.conf
+ldconfig
+------------------------------------------------------------------------------
+
+5. 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 <osname>-developer Makefile.install target. Currently,
+ this is only needed for building and installing the (preview) browser
+ staff client.
++
+[source, bash]
+------------------------------------------------------------------------------
+make -f Open-ILS/src/extras/Makefile.install <osname>-developer
+------------------------------------------------------------------------------
++
+ * To install packages required for building Evergreen translations, use
+ the <osname>-translator Makefile.install target.
++
+[source, bash]
+------------------------------------------------------------------------------
+make -f Open-ILS/src/extras/Makefile.install <osname>-translator
+------------------------------------------------------------------------------
++
+ * To install packages required for building Evergreen release bundles, use
+ the <osname>-packager Makefile.install target.
++
+[source, bash]
+------------------------------------------------------------------------------
+make -f Open-ILS/src/extras/Makefile.install <osname>-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 previously described
+'Optional: Developer Additions'. You will still need to do the following
+steps in <<install_files_for_web_staff_client,Install files for web staff client>>.
+
+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`.
++
+2. Install Grunt CLI
++
+[source,sh]
+------------------------------------------------------------------------------
+% sudo npm install -g grunt-cli
+------------------------------------------------------------------------------
+
+[[install_files_for_web_staff_client]]
+Install 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
+grunt all
+------------------------------------------------------------------------------
+
+
+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, build the server
+ portion of the staff client, and copy example configuration files to
+ `/openils/conf`.
+ Change the value of the `STAFF_CLIENT_STAMP_ID` variable to match the version
+ of the staff client that you will use to connect to the Evergreen server.
++
+[source, bash]
+------------------------------------------------------------------------------
+make STAFF_CLIENT_STAMP_ID=rel_3_0_1 install
+------------------------------------------------------------------------------
++
+2. The server portion of the staff client expects `http://hostname/xul/server`
+ to resolve. Issue the following commands as the *root* Linux account to
+ create a symbolic link pointing to the `server` subdirectory of the server
+ portion of the staff client that we just built using the staff client ID
+ 'rel_name':
++
+[source, bash]
+------------------------------------------------------------------------------
+cd /openils/var/web/xul
+ln -sf rel_name/server server
+------------------------------------------------------------------------------
+
+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 in `Open-ILS/examples/apache/` (for
+Apache versions below 2.4) or `Open-ILS/examples/apache_24/` (for Apache
+versions 2.4 or greater) to configure your Web server for the Evergreen
+catalog, staff client, Web services, and administration interfaces. Issue the
+following commands as the *root* Linux account:
++
+.Debian Wheezy
+[source,bash]
+------------------------------------------------------------------------------
+cp Open-ILS/examples/apache/eg.conf /etc/apache2/sites-available/
+cp Open-ILS/examples/apache/eg_vhost.conf /etc/apache2/
+cp Open-ILS/examples/apache/eg_startup /etc/apache2/
+# Now set up SSL
+mkdir /etc/apache2/ssl
+cd /etc/apache2/ssl
+------------------------------------------------------------------------------
++
+.Ubuntu Trusty/Xenial and Debian Jessie/Stretch
+[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/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 staff client
+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):
+ * (Apache 2.2): Replace `Allow from 10.0.0.0/8` with `Allow from all`
+ * (Apache 2.4): Replace `Require host 10.0.0.0/8` with `Require all granted`
+. Change the user for the Apache server.
+ * (Debian and Ubuntu): 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.
+ * (Debian and Ubuntu): 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:
++
+.Debian Wheezy (`/etc/apache2/apache2.conf`)
+[source,bash]
+------------------------------------------------------------------------------
+<IfModule mpm_prefork_module>
+ StartServers 15
+ MinSpareServers 5
+ MaxSpareServers 15
+ MaxClients 75
+ MaxRequestsPerChild 500
+</IfModule>
+------------------------------------------------------------------------------
++
+.Ubuntu Trusty/Xenial, Debian Jessie/Stretch (`/etc/apache2/mods-available/mpm_prefork.conf`)
+[source,bash]
+------------------------------------------------------------------------------
+<IfModule mpm_prefork_module>
+ StartServers 15
+ MinSpareServers 5
+ MaxSpareServers 15
+ MaxRequestWorkers 75
+ MaxConnectionsPerChild 500
+</IfModule>
+------------------------------------------------------------------------------
++
+. (Ubuntu Trusty/Xenial, Debian Jessie/Stretch) As the *root* user,
+ enable the mpm_prefork module:
++
+[source,bash]
+------------------------------------------------------------------------------
+a2dismod mpm_event
+a2enmod mpm_prefork
+------------------------------------------------------------------------------
++
+. (Debian Wheezy): As the *root* Linux account, enable the Evergreen site:
++
+[source,bash]
+------------------------------------------------------------------------------
+a2dissite default # OPTIONAL: disable the default site (the "It Works" page)
+a2ensite eg.conf
+------------------------------------------------------------------------------
++
+(Ubuntu Trusty/Xenial, Debian Jessie/Stretch):
++
+[source,bash]
+------------------------------------------------------------------------------
+a2dissite 000-default # OPTIONAL: disable the default site (the "It Works" page)
+a2ensite eg.conf
+------------------------------------------------------------------------------
++
+. (Debian and Ubuntu): 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:
+
+.(Debian / Ubuntu) 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-<OSTYPE>'. 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-debian-wheezy
+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 <user>, <password>,
+<hostname>, <port>, and <dbname> with the appropriate values for your
+PostgreSQL database (where <user> and <password> are for the *evergreen*
+PostgreSQL account you just created), and replace <admin-user> and <admin-pass>
+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 <user> --password <password> --hostname <hostname> --port <port> \
+ --database <dbname> --admin-user <admin-user> --admin-pass <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 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 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 <admin-user> <admin-pass>
+------------------------------------------------------------------------------
+
+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.
projects / evergreen / pines.git / commitdiff