From b253f46fddf27d47df6ba151affeff352c824a27 Mon Sep 17 00:00:00 2001 From: Steve Sheppard Date: Thu, 12 Aug 2010 17:42:31 -0400 Subject: [PATCH] new file; --- 1.6/admin/ServersideInstallation.xml | 603 +++++++++++++++++++++++++++++++++++ 1 file changed, 603 insertions(+) create mode 100644 1.6/admin/ServersideInstallation.xml diff --git a/1.6/admin/ServersideInstallation.xml b/1.6/admin/ServersideInstallation.xml new file mode 100644 index 0000000000..b0408bf3be --- /dev/null +++ b/1.6/admin/ServersideInstallation.xml @@ -0,0 +1,603 @@ + + + + Server-side Installation of Evergreen Software + + Specifics in the process of installing server-side software for Evergreen + + +
+ Overview + A bare-minimum system Evergreen system requires only a single Server and a single Staff Client (in fact, that is a reasonable system for simple experiments or a proof-of-concept). Another simple system may require only that you install one or more instances of the Staff Client software. For instance, if your consortium already provides the Evergreen Server software or if you are using the hosted version provided by Equinox, you do not need to install the Server software at all. But typical real-world systems will probably consist of at least one or two Servers plus multiple Staff Clients. + The Server software currently runs as a native application on any of several well-known Linux distributions (e.g., Debian and Ubuntu). It does not run as a native application on the Windows operating system (e.g., WindowsXP, WindowsXP Professional, Windows7), but the software can be installed and run on Windows via a virtualized Unix-guest Operating System (using, for example, VirtualBox or VMware to emulate a Linux environment). More information on virtualized environments can be found in the section "Installing in Virtualized Unix Environments" +
+
+ System Requirements + This section describes processes and events that must occur to install the Evergreen server in all supported operating systems / environments. Please review the section "The Installation Process" for instructions tailored to specific distributions. + The system requirements for running Evergreen really depend on what you want to do with it. For just evaluating the software, or for a very small library (for example, 1 circulation station, a few thousand items, and infrequent online catalog use), any modern desktop or laptop made within the last few years capable of running Linux, FreeBSD, etc. should suffice. We recommend at least 512mb of RAM. + + + From Dan Scott on [http://list.georgialibraries.org/pipermail/open-ils-general/2007-July/000316.html|OPEN-ILS-GENERAL]: + > On 8/11/07, lan ye <lye at mail.slcl.org> wrote: + > > We've been researching the Evergreen Open Source Library system, and would + > like to have a list of hardware requirements for the installation of a small + > test server. To keep things within a small budget, I would like to just use + > an ordinary PC. Could you send some information to us? + + For system requirements, it depends on how extensive you want your + tests to be. Evergreen and all of the pieces it depends on + (PostgreSQL, Apache, Ejabberd) run happily in a VMWare image allocated + 512MB of RAM on my laptop with just the Project Gutenberg e-books + loaded, and that's enough to evaluate the OPAC interface / try out the + staff client / make some local changes and generally experiment. But + I'm not going to load one million bib records into that system and + expect it to perform. So, probably any hardware you have lying around + would be adequate for a small test server. + + > > It looks like Evergreen has been successfully installed on two Linux + > systems: Gentoo and Ubuntu. Which one is the best for us to test using + > what's already in place at other libraries? Are there any differences / + > Advantages in functionality between Gentoo and Ubuntu? + + As John said, GPLS is running on Debian, and that's the only Evergreen + system that is in production at the moment. However, the documentation + for installing on Debian is a bit scattered right now. The developers + themselves used Gentoo originally, and that's what I'm using at the + moment & have documented in the wiki; the install process on Ubuntu is + very thoroughly documented and Ubuntu is reasonably close to Debian. + See http://open-ils.org/dokuwiki/doku.php?id=server_installation for + the list of install instructions for various distributions. + + As for advantages / disadvantages of particular distributions, that's + a religious war that I don't want to step into... We'll try to help + you out no matter what distribution you choose; just please choose a + current release :) + + -- + Dan Scott + Laurentian University + + + And from James Fournie in that same [http://list.georgialibraries.org/pipermail/open-ils-general/2007-July/000317.html|thread]: + We are running a test Ubuntu server on a ~1ghz Celeron PC with 512mb RAM. + It seems to be ok handling the Gutenberg samples, and our collection of + about 8000 records. We did have serious problems using anything less than + 512mb RAM. Also, I tried Evergreen on a K6 II 350, but it wasn't pretty. + + James Fournie + Digitization Librarian + Union of B.C. Indian Chiefs + + +
+
+ Example System Architectures + [[real-world examples of working systems]] +
+ PINES + In order to provide load balancing and high-availability at the OPAC and Staff Client level, PINES has implemented a Linux Virtual Server environment with five independent mini-clusters. This allows live updates of the entire system with no perceived downtime or interruption in service. + [[ further information on PINES ]] +
+
+ Other Architectures + [[ further information on OTHER ]] +
+
+
+ Installing in Virtualized Unix Environments + [[ Installing in Virtualized Unix Environments ]] +
+ VirtualBox + [[ VirtualBox ]] +
+
+ VMware + [[ VMware ]] +
+
+ VirtualPC + [[ VirtualPC ]] +
+
+
+ The Installation Process +
+ Current stable Release + + Installing Evergreen 1.6.0.x on Ubuntu or Debian + + + Installing OpenSRF 1.2.x + +
+
+ Previous stable release + + Installing Evergreen 1.4.0.x on Ubuntu or Debian + + + Installing OpenSRF 1.0.x + +
+
+ Configuring the system + + Organization and Policy Editing + +
+ Holds + For holds to work properly, you need to run this command as the user opensrf to calculate the proximity of locations in the Organizational Unit tree: + + $ autogen.sh -u -c /openils/conf/opensrf_core.xml + + This is an expensive operation if you have a large Organizational Unit tree, so don't run it indiscriminately. +
+
+
+
+ Installing Evergreen 1.6.0.x On Ubuntu or Debian + The following steps have been tested on the x86 (32-bit) and x86-64 (64-bit) architectures. There may be differences between the Desktop and Server editions of Ubuntu. These instructions assume the Server edition. + In the following instructions, you are asked to perform certain steps as either the root user, the opensrf user, or the postgres user. + To become the root user, issue the command: sudo su - root. To switch from the root user to a different user, issue a command like: su - USERNAME. For example, to switch from the root user to the opensrf user, issue this command: su - opensrf. Once you have become a non-root user, to become the root user again, simply issue the exit command. +
+ Install the latest version of OpenSRF + For further information on installing the Open Service Request Framework (OpenSRF), see the section Installing OpenSRF. + Follow the steps outlined in that section, then run the specified test(s) to ensure that OpenSRF is properly installed before continuing with any further Evergreen installation steps. The Evergreen application depends on properly installation of OpenSRF. If OpenSRF does not work correctly, Evergreen will not work properly either. +
+
+ Download and Build Evergreen + In this section, you will download, unpack, install and test the Evergreen system, including the Evergreen server and the PostgreSQL database system. You will also make several configuration changes and adjustments to the software, including updates to configure the system for your own locale, and some updates needed to work around a few known issues. + As far as possible, perform the following steps in the order they are given, since the success of many steps relies on the successful completion of earlier steps. You should make backup copies of files and environments when you are instructed to do so. In the event of installation problems, those copies can allow you to back out of a step gracefully and resume the installation from a known state. + Of course, when you successfully complete and test the entire installation you should take a final snapshot backup of your system(s). This can be the first in the series of regularly scheduled system backups that you should probably institute. +
+ Download and Unpack Latest Evergreen Version + As the opensrf user, download and extract the latest version of Evergreen. The latest version can be found here: +
+ Commands to download/extract Evergreen + + $ sudo su - opensrf + $ wget http://evergreen-ils.org/downloads/Evergreen-ILS-1.6.0.7.tar.gz + $ tar zxf Evergreen-ILS-1.6.0.7.tar.gz + +
+
+
+ Install Prerequisites to Build Evergreen + In this step you will install and configure a set of prerequisites for building Evergreen. In a following step you will actually build the software. + As the root user, build the prerequisites from the software distribution that you just downloaded and unpacked. Enter the commands show below. Remember to replace [distribution] in the following example with the keyword that corresponds to your actual Linux distribution (see the following list): + + debian-etch for Debian Etch (4.0) + debian-lenny for Debian Lenny (5.0) + [[other Debian distributions]] + ubuntu-hardy for Ubuntu Hardy (8.04) + ubuntu-karmic for Ubuntu Karmic (9.10) and Ubuntu Lucid (10.04) + [[other Ubuntu distributions]] + +
+ Commands to install prerequisites for Evergreen + + $ sudo su - root + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + $ make -f Open-ILS/src/extras/Makefile.install [distribution] + +
+
+
+ (OPTIONAL) Install the PostgreSQL Server + Since the PostgreSQL server is usually a standalone server in multi-server production systems, the prerequisite installer Makefile in the previous step does not automatically install PostgreSQL. If your PostgreSQL server is on a different system, just skip this step. + For further information on installing PostgreSQL, see the section Installing PostgreSQL. + If your PostgreSQL server will be on the same system as your Evergreen software, then as the root user install the required PostgreSQL server packages: +
+ Commands to install the PostgreSQL server + + $ sudo su - root + + # Debian Lenny and Ubuntu Hardy (8.04) + $ make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_debs_83 + + # Ubuntu Karmic (9.10) and Ubuntu Lucid (10.04) + $ make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_debs_84 + +
+ Note: PostgreSQL 8.1 is deprecated and will become unsupported in a future release, though existing installations upgrading from Evergreen 1.4 or before will work fine. However, consider upgrading your Postgres soon! + [[ is this still true? ]] + [[ how to determine which version of PostgreSQL you have? ]] +
+
+ (OPTIONAL) Install Perl Modules on PostgreSQL Server + If PostgreSQL is running on the same system as your Evergreen software, then the Perl modules will automatically be available. Just skip this step. + Otherwise, if your PostgreSQL server is running on another system, then as the root user install the following Perl modules on that system: +
+ Commands to install Perl modules + + # ensure the gcc compiler is installed + $ sudo su - root + $ aptitude install gcc + + # install the Perl modules + $ perl -MCPAN -e shell + cpan> install JSON::XS + cpan> install MARC::Record + cpan> install MARC::File::XML + +
+ [[ how to install the Perl modules ]] + [[ how to verify that the Perl modules are installed ]] +
+
+ Add Additional Library Paths on Evergreen System + As the root user, you must update the system dynamic library path to ensure the system will recognize the newly installed libraries. Do this by creating a new file named /etc/ld.so.conf.d/eg.conf containing the two paths, then run the command ldconfig to automatically read the file and modify the dynamic library path: +
+ Commands to modify system dynamic library path + + $ sudo su - root + $ cat > /etc/ld.so.conf.d/eg.conf << ENDOFFILE + /usr/local/lib + /usr/local/lib/dbd + ENDOFFILE + $ ldconfig + +
+
+
+ (OPTIONAL) Restart the PostgreSQL Service + If PostgreSQL is running on the same system as the rest of Evergreen, as the root user you must restart the PostgreSQL service to avoid a problem where the library plperl.so cannot be found. If your PostgreSQL server is running on another system, just skip this step. + [[ other versions of PostgreSQL ]] +
+ Commands to restart PostgreSQL service + + $ sudo su - root + $ /etc/init.d/postgresql-8.3 restart + +
+
+
+ Configure and Compile Evergreen Sources + As the opensrf user, configure and compile the software from the prerequisites that were set up in previous steps: +
+ Commands to configure and compile Evergreen + + $ sudo su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + $ ./configure --prefix=/openils --sysconfdir=/openils/conf + $ make + +
+
+
+ Link and Install Evergreen + As the root user, link and install the compiled code. In the commands below, remember to set the variable STAFF_CLIENT_BUILD_ID to match the version of the staff client you will use to connect to the Evergreen Server. Finally, create a symbolic link named server in /openils/var/web/xul to the /server subdirectory of your staff client build: +
+ Commands to link and install Evergreen + + $ sudo su - root + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + $ make STAFF_CLIENT_BUILD_ID=rel_1_6_0_6 install + $ cd /openils/var/web/xul + $ ln -sf rel_1_6_0_7/server server + +
+
+
+ Copy the OpenSRF Configuration Files + As the root user, copy the example OpenSRF configuration files into place. This will replace the OpenSRF configuration files that you set up while installing and testing OpenSRF. You should also create backup copies of the old files for troubleshooting purposes. Finally, change the ownership on the installed files to the user opensrf: +
+ Commands to copy OpenSRF configuration files + + $ sudo su - root + $ cp /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml + $ cp /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml + $ cp /openils/conf/oils_web.xml.example /openils/conf/oils_web.xml + $ chown -R opensrf:opensrf /openils/ + +
+
+
+ Create and configure PostgreSQL Database + As the postgres user on your PostgreSQL server, create the Evergreen database. + Remember to adjust the path for the contrib repository to match your PostgreSQL server layout. For example, if you built PostgreSQL from source following the cheat sheet, the contrib directory will be located here: /usr/local/share/contrib . If you installed the PostgreSQL 8.3 server packages on Ubuntu 8.04, the directory will be located here: /usr/share/postgresql/8.3/contrib/ . + + + + Create and configure the database + + As the postgres user on the PostgreSQL system create the PostgreSQL database, then set some internal paths: +
+ Commands to create database and adjust the path + + # create the database + $ sudo su - postgres + $ createdb -E UNICODE evergreen + $ createlang plperl evergreen + $ createlang plperlu evergreen + $ createlang plpgsql evergreen + + # adjust the paths + $ psql -f /usr/share/postgresql/8.3/contrib/tablefunc.sql evergreen + $ psql -f /usr/share/postgresql/8.3/contrib/tsearch2.sql evergreen + $ psql -f /usr/share/postgresql/8.3/contrib/pgxml.sql evergreen + +
+ + + Create new Evergreen superuser + As the postgres user on the PostgreSQL system, create the new user evergreen : +
+ Commands to create the 'evergreen' user + + # create superuser 'evergreen' and set the password + $ sudo su - postgres + $ createuser -P -s evergreen + Enter password for new role: mynewpassword + Enter it again: mynewpassword + +
+ + +
+
+ Create Database Schema + As the root user, create the database schema and configure your system with the corresponding database authentication details for the database user 'evergreen' that you created in the previous step. + Enter the commands and replace [HOSTNAME], [PORT], [USER], [PASSWORD] and [DATABASENAME] with appropriate values. + On most systems [HOSTNAME] will be localhost, and [PORT] will be 5432. +
+ Commands to create Evergreen database schema + + $ sudo su - root + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + $ perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config \ + --service all --create-schema --create-bootstrap --create-offline \ + --hostname [HOSTNAME] --port [PORT] \ + --user [USER] --password [PASSWORD] --database [DATABASENAME] + +
+ + NOTE: If you are entering the above command on a single line, do not include the ''\'' characters. If you are using the bash shell, these should only be used at the end of a line at a bash prompt to indicate that the command is continued on the next line. + +
+
+ Setup the Apache Server + As the root user, configure the Apache server and copy several new configuration files to the Apache server directories: +
+ Commands to configure the Apache server + + # configure the Apache server + $ sudo su - root + $ a2enmod ssl # enable mod_ssl + $ a2enmod rewrite # enable mod_rewrite + $ a2enmod expires # enable mod_expires + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + + # copy files + $ 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/startup.pl /etc/apache2/ + +
+
+
+ Create a Security Certificate (SSL Key) + Use the command openssl to create a new SSL key for your Apache server. For a public production server you should configure or purchase a signed SSL certificate, but for now you can just use a self-signed certificate and accept the warnings in the staff client and browser during testing and development: +
+ Commands to create an SSL key + + $ mkdir /etc/apache2/ssl + $ cd /etc/apache2/ssl + $ openssl req -new -x509 -days 365 -nodes -out server.crt -keyout server.key + +
+ Warning: This is only a temporary measure to expedite testing. You must get a proper SSL certificate for a public production system. See this section for further comments on setting up a properly signed SSL certificate: + [[how to get a signed SSL certificate]] +
+
+ Modify the Apache Configuration File + Edit the Apache configuration file /etc/apache2/sites-available/eg.conf and make the following changes: + + + Comment out the line Allow from 10.0.0.0/8, then uncomment the line Allow from all. This is a temporary measure to expedite testing. + + Warning: You must remove these changes after testing is completed. This will enable access to the configuration CGI scripts from any workstation on any network. You must secure this for a public production system, preferably by explicitly specifying the allowed IP addresses and adding proper authentication. + + + Comment out the line Listen 443 as it conflicts with the same declaration in the configuration file: /etc/apache2/ports.conf . + [[Debian Etch users - do not do this!]] + +
+
+ Modifications to Keep the Logs Functioning + You must modify the Apache configuration file to allow the logs to function properly, but it may break other Apache applications on your server. We hope to make this unnecessary soon. + [[ is this still necessary ? ]] + + + For the Linux distributions Ubuntu Hardy / Debian Etch , as the root user, edit the Apache configuration file /etc/apache2/apache2.conf and change the user: + www-data + to the user: + opensrf + + + For the Linux distributions Ubuntu Karmic / Ubuntu Lucid / Debian Lenny , as the root user, edit the Apache configuration file /etc/apache2/envvars and change the phrase: + export APACHE_RUN_USER=www-data + to the phrase: + export APACHE_RUN_USER=opensrf + + +
+
+ Modify Apache Configuration File + As the root user, edit the Apache configuration file /etc/apache2/apache2.conf and add the line KeepAliveTimeout 1, or modify an existing line if it already exists. +
+
+ (OPTIONAL) Performance Modifications for Apache + As the root user, edit the Apache configuration file /etc/apache2/apache2.conf and add the line MaxKeepAliveRequests 100, or modify an existing line if it already exists. Additionally, locate and modify the section related to prefork configuration to suit the load on your system. + Following are settings that may apply to a busy system: +
+ "Prefork configuration" section of Apache configuration file + + <IfModule mpm_prefork_module> + StartServers 20 + MinSpareServers 5 + MaxSpareServers 15 + MaxClients 150 + MaxRequestsPerChild 10000 + </IfModule> + +
+ [[ settings of "prefork configuration" section for busy/notbusy systems ]] +
+
+ Enable the Evergreen Site + As the root user, enable the Evergreen site: +
+ Commands to enabl e the Evergreen site + + $ sudo su - root + $ a2dissite default # OPTIONAL: disable the default site (i.e., the "It Works" page). + $ a2ensite eg.conf + +
+
+
+ Modify the OpenSRF Configuration File + As the opensrf user, edit the OpenSRF configuration file /openils/conf/opensrf_core.xml to update the Jabber usernames and passwords, and to specify the domains from which we'll accept and to which we'll make connections. + If you are installing Evergreen on a single server and using the ~private.localhost~ / ~public.localhost~ domains, these will already be set to the correct values. Otherwise, search and replace to match your customized values. + Note: the following example uses common XPath syntax on the left-hand side to indicate the position within the XML file: +
+ Updates needed to the file /openils/conf/opensrf_core.xml + + /config/opensrf/username = opensrf + /config/opensrf/passwd = password for **private.localhost** opensrf user + /config/gateway/username = opensrf + /config/gateway/passwd = password for **public.localhost** opensrf user + /config/routers/router/transport - first entry, where ''transport/server'' == **public.localhost** : + username = router + password = password for **public.localhost** router user + /config/routers/router/transport'' - second entry, where ''transport/server'' == **private.localhost** : + username = router + password = password for **private.localhost** router user + +
+ [[ better diagram needed here ]] +
+
+ Create Private Configuration Files for Certain Users + Copy the file /openils/conf/srfsh.xml.example to the file .srfsh.xml in the home directory of each user you want to use to run the srfsh command line client for testing OpenSRF. Finally, edit each file .srfsh.xml and make the following changes: + + Modify domain to be the router hostname (following our domain examples, private.localhost will give the utility srfsh access to all OpenSRF services, while public.localhost will only allow access to those OpenSRF services that are publicly exposed). + Modify username and password to match the opensrf Jabber user for the chosen domain + Modify logfile to be the full path for a log file to which the user has write access + Modify loglevel as needed for testing + +
+ Sample of configuration file /openils/conf/srfsh.xml.example + + <?xml version="1.0"?> + <!-- This file follows the standard bootstrap config file layout found in opensrf_core.xml --> + <srfsh> + <router_name>router</router_name> + <domain>private.localhost</domain> + <username>opensrf</username> + <passwd>evergreen</passwd> + <port>5222</port> + <logfile>/tmp/srfsh.log</logfile> + <!-- 0 None, 1 Error, 2 Warning, 3 Info, 4 debug, 5 Internal (Nasty) --> + <loglevel>4</loglevel> + </srfsh> + +
+
+
+ Modify the OpenSRF Environment + As the opensrf user, change the permissions of files to executable in the directory /openils/var/cgi-bin, then add a Perl environmental variable to the shell configuration file ~/.bashrc for the user opensrf. + Note: in a multi-server environment, you must add the modifications to ~/.bashrc at the top of the file before the line [ -z "$PS1" ] && return. This will allow headless (scripted) logins to load the correct environment. +
+ Modify the OpenSRF environment + + # change permissions + $ sudo su - opensrf + $ chmod 755 /openils/var/cgi-bin/*.cgi + + # add environmental variable + $ echo "export PERL5LIB=/openils/lib/perl5:\$PERL5LIB" >> ~/.bashrc + $ . ~/.bashrc # inherit the new environment + +
+
+
+ (OPTIONAL) Configuration for Other Languages + Load translations such as Armenian (hy-AM), Canadian French (fr-CA), and others into the database to complete the translations available in the OPAC and staff client. See [[server_installation:adding_localizations|these instructions]] for details. +
+
+
+ Starting the Server +
+
+ Testing Connections to the Server +
+
+ Starting the Web Server +
+
+ Stopping the Server +
+
+ Setting Up Support For Reports +
+
+
+ Installing OpenSRF 1.2.x + [[ Installing OpenSRF 1.2.x ]] +
+
+ Installing Evergreen 1.4.0.x on Ubuntu or Debian + [[ Installing Evergreen 1.4.0.x on Ubuntu or Debian ]] +
+
+ Installing OpenSRF 1.0.x + [[ Installing OpenSRF 1.0.x ]] +
+
+ Organization and Policy Editing + [[ Organization and Policy Editing ]] +
+
+ Testing the Installation +
+ Testing with srfsh + Installing OpenILS will place an executable called 'srfsh' (surf shell) into the BINDIR directory. This is a command line diagnostic tool for interacting with the OpenSRF network. + For starters, there is a command called math_bench in srfsh that sends queries to the math servers. Note that opensrf.math and opensrf.dbmath must be running for this command to work: + + srfsh# math_bench 10 + |.........|.........|.........|.........|.........|.........|.........|.........|.........|......... + + ++++++++++++++++++++++++++++++++++++++++ + Average round trip time: 0.033425 + srfsh# + + The first argument is how many sets of 4 queries (+ - * /) are sent to opensrf.math. When the response is successful, you will see the string of "+" symbols. If the system is not running correctly, you will either get an exception or no result at all. + For other srfsh commands, type 'help' in at the prompt. +
+
+ Testing the OPAC + By default, the OPAC will live at the URL http://my.domain.com/opac/. + Navigate to this URL and the front page of the OPAC should load. There is a basic text entry field with some extra search options. If you have any problems loading this page, check the Apache error logs. If the page loads but does not function correctly, then check for possible javascript errors. We hightly reccommend testing with the Firefox browser because of the helpful javascript debugging tools. + Assuming that the OPAC is functioning and there is data in your database, you can now perform other simple functional tests (e.g., searching the catalog). + [[ other simple functional tests ]] +
+
+
+ Building the Staff Client + [[ Building the Staff Client ]] +
+
+ Language Localization + [[ Adding Localized Languages to the Database ]] +
+
+ Installing the SIP Server + [[ Installing the SIP Server ]] +
+
+ Using nginx to serve static content + [[ Using nginx to serve static content ]] +
+ -- 2.11.0