Editing Non-root proxy (section)

===ePrints===
Before you can install ePrints, you need to check the Package requirements.
CGI.pm builds against the installed Mod-Perl modules, so may well be wrong. You may need to install your own version.

eg:
<pre>

%> /path/to/specific/perl -MCPAN -e shell
[snip]
cpan> install CGI
[...]
cpan> quit

</pre>

Now we can install the ePrints software (previously downloaded into ~/distributions):

<pre>

%> cd ~/distributions/
%> tar xvf eprints-3.zzz.tar
%> cd eprints-3.zzz./

</pre>

There is no option to clean a previously configured eprints tree, so keep going..
<pre>

%> ./configure --prefix=/home/MyUser/ePrints --with-perl=/path/to/specific/perl --with-user=MyUser \
    --with-group=MyUserGroup -with-toolpath=/path/to/tools --disable-diskfree \
    --with-smtp-server=your.mail.server

</pre>

Note: the same version of perl is being defined again, and the <code>/path/to/tools</code> is a directory to find various external tools (<code>tar</code>, <code>wget</code>, <code>(g)unzip</code>, <code>pdftotext</code>, <code>lynx</code>, etc)

<p>... and install:</p>
<pre>

%> ./install.pl

</pre>

As we do not have root access to the MySQL database, you will need to get the database administrator to add a user to provide access the MySQL database. Note: Assuming your user is not given <code>GRANT ALL</code> (its a big security risk) you will need <code>CREATE TEMPORARY TABLES</code> as well as <code>CREATE</code> privilages.

====Create the basic repository====

The trick here is to install a basic eprint repository to match the web server (installed above), and then alter the core configuration to reflect the proxy settings.

<pre>

%> cd /home/MyUser/ePrints

</pre>

We also know that the service is going to run as a local user, so the file and directory permissions need to be altered

These are all defined in the file <code>perl_lib/EPrints/SystemSettings.pm</code>:
<pre>
$EPrints::SystemSettings::conf = {
                                       // snip //
                                    'file_perms' => 0640,
                                       // snip //
                                    'dir_perms' => 0775
</pre>

In EPrints 3, all the configuration is done using the <code>bin/epadmin</code>.

* Initial configuration

'''NOTE:''' EPrints assumes a MySql backend, and the configuration routines assume it. This means that you need to have the mysql libraries available to the perl routines during this process. You may setup a Postgres, Oracle, or "Cloud" storage system once the basic configuration is in place, but you need mysql to kick-start the process.

'''NOTE''' In my install, all the <code>bin/</code> files are installed with <code>/usr/bin/perl</code>, not whatever's defined in the .configure statement - you may need to edit them!

The command to create the basic framework for a repository is:

<pre>
bin/epadmin create
</pre>

* When asked <code>Configure vital settings? [yes] ?</code>, say "Yes" and fill in the details
** <code>Hostname?</code> is the actual address of the web server created above, not the public address (we fix that later) - so '''services.example.com'''
** <code>Webserver Port [80] ?</code> is the actual address of the web server created above, not the port for the web server (we fix that later) - so '''1234'''
** <code>Archive Name [Test Repository] ?</code> is the name that the EPrints.org system will use when it dynamically supplies the archive name (using the &lt;epc:pin /&gt; coding)

* When asked <code>Configure database? [yes] ?</code>, say "Yes" and fill in the details
** <code>Database Name</code> is the name of the database created for you by the database admin people
** <code>MySQL Host</code> is the hostname for the server
** <code>MySQL Port</code> <code>MySQL Socket</code> can probably be left blank, but check with the database admin people
** <code>Database User</code> <code>Database Password</code> is as per agreed with the database admin people
* <code>Create database "Deposit"</code> <b>NO</b> - you can't, as we don't have that level of access to the database.

Now we need to do the rest of the building-work manually:

When using a database that's '''not''' mysql, then you need to tell EPrints what driver to use.
* Edit <pre> archives/<ARCHIVEID>/cfg/cfg.d/database.pl </pre> and add <pre> $c->{dbdriver} = "xxxx"; </pre> where '''xxx''' is the appropriate Perl DBD package (eg '''Pg''' for postgreSQL)

* Create the database tables: <pre> bin/epadmin create_tables <ARCHIVEID> </pre>
* Create users (I suggest an admin user and a normal user): <pre> bin/epadmin create_user <ARCHIVEID> </pre> 
* Build the subject tables: <pre> bin/import_subjects <ARCHIVEID> <path/to/subject/file></pre> Either use <code>lib/defaultcfg/subjects</code> for the shipped '''Library Of Congress''' tree, or download a subject tree from [http://files.eprints.org files.eprints.org]
* Create the static web pages for a basic web site: <pre> bin/generate_static <ARCHIVEID> </pre> 
* Create pages of abstracts: <pre> bin/generate_abstracts <ARCHIVEID> </pre> (should do nothing, as there are no abstracts in the system)
* Create the browse pages: <pre> bin/generate_views <ARCHIVEID> </pre>

====Configuring the repository:====

EPrints has a global Apache configuration file, and then separate config files for each &lt;ARCHIVEID&gt; archive running under the web server

To be sure of the correct config files for your particular install (we are discovering that they seem to move around depending on version), do the following command:

<pre> cd /home/MyUser/ePrints
 find ./ -name *.conf -print
</pre>

Generate the apache configuration files.

<pre> cd /home/MyUser/ePrints
 bin/generate_apacheconf </pre>

Edit httpd.conf

* Remove the document root and cgi-bin stuff from the httpd.conf file (the name and the <directory> section) - these are set on a per-repository basis
* Include the generated apache.conf:

<pre>

# EPrints
Include /home/MyUser/ePrints/cfg/apache.conf

</pre>




EPrints produces absolute URLs for everything (<code>http://web.host.name/</code>), so we need to ensure that the repository uses the correct address. Edit <code>archives/<i>ARCHIVEID</i>/cfg/cfg.d/10_core.pl</code>
<pre>
$c->{host} = 'eprints.example.com';
$c->{port} = '80';

</pre>

====Fix a bug-ette====
There is a problem that has been found on a number of systems where the system goes into a loop of reporting
<pre> [warn] (128)Network is unreachable: connect to listener on [::]:<PORTNO></pre>

The solution is to alter the "Listen" directive to include an IP number. Either use the IP number for the host, or cheat:
<pre>
  Listen: 0.0.0.0:<PORTNO>

</pre>

Start web server.  Check the error log:

<pre>

%> cat ~/www/logs/error_log
[...] Apache/2.2.0 (Unix) Configured -- resuming normal operations
[...] caught SIGTERM, shutting down
[...] Apache/2.2.0 (Unix) mod_perl/2.0.2 Perl/v5.8.0 configured -- resuming normal operations
[...] [notice] caught SIGTERM, shutting down
EPrints archives loaded: <ARCHIVEID>
EPrints archives loaded: <ARCHIVEID>
[...] Apache/2.2.0 (Unix) mod_perl/2.0.2 Perl/v5.8.0 configured -- resuming normal operations

</pre>