Editing Non-root proxy (section)

====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>