Non-root proxy - Revision history

Kiz: /* Mod-Perl */

2013-10-22T09:48:18Z

‎Mod-Perl

2013-10-21T14:41:51Z

‎Mod-Perl

2013-10-08T10:19:44Z

‎Create the basic repository

2013-10-08T10:19:08Z

‎Create the basic repository

2013-06-03T11:02:43Z

‎Configuring the repository:

2013-06-03T10:53:02Z

‎Configuring the repository:

2013-06-03T10:52:37Z

‎Create the basic repository

2013-06-03T10:51:16Z

‎Task

2013-06-03T10:50:47Z

‎Task

2013-06-03T10:48:50Z

‎Task

@@ Line 75: / Line 75: @@
     MP_APXS="/home/MyUser/www/bin/apxs" \
     MP_AP_CONFIGURE="--prefix=/home/MyUser/www --disable-userdir \
-    --disable-status --enable-module=mod-perl"
+    --disable-status --enable-module=mod_perl"
 %> make
 %> make install

← Older revision		Revision as of 14:41, 21 October 2013
Line 80:		Line 80:

	</pre>		</pre>
		+	NOTE: To install under Debian/Ubuntu, you will need the <code>libperl-dev</code> package installed

	NOTE: Notice that there is a PREFIX defined, which matches the prefix in the CPAN configuration; that we are stating we want mod-perl as a DSO; the full path to the previously installed Apache "apxs" command; and that the configure parameters to be passed to the apache rebuild include enabling mod-perl		NOTE: Notice that there is a PREFIX defined, which matches the prefix in the CPAN configuration; that we are stating we want mod-perl as a DSO; the full path to the previously installed Apache "apxs" command; and that the configure parameters to be passed to the apache rebuild include enabling mod-perl

@@ Line 197: / Line 197: @@
 '''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.
+'''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:

← Older revision		Revision as of 10:19, 8 October 2013
Line 196:		Line 196:

	'''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:''' 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.

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

@@ Line 242: / Line 242: @@
   bin/generate_apacheconf </pre>
-Edit httpd.conf to include the generated apache.conf:
+Edit httpd.conf
 <pre>
@@ Line 251: / Line 254: @@
 </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>

@@ Line 264: / Line 264: @@
 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} = 'public.host.name.org';
+$c->{host} = 'eprints.example.com';
 $c->{port} = '80';

@@ Line 204: / Line 204: @@
 * 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)
+** <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)
+** <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)

@@ Line 5: / Line 5: @@
 [[Image:Webserver_proxy.png]]
-We will build the web server on a private computer called services.example.com, running on port 1234; and the public access will be eprints.example.com, on port 80
+We will build the web server on a private computer called ''services.example.com'', running on port ''1234''; and the public access will be ''eprints.example.com'', on port ''80''
 ===Preparation===

← Older revision		Revision as of 10:50, 3 June 2013
Line 4:		Line 4:

	[[Image:Webserver_proxy.png]]		[[Image:Webserver_proxy.png]]
		+
		+	We will build the web server on a private computer called services.example.com, running on port 1234; and the public access will be eprints.example.com, on port 80

	===Preparation===		===Preparation===

@@ Line 3: / Line 3: @@
 To build Apache 2 &amp; mod_perl 2 for ePrints 3, installed as a standard user, with no superuser-like access to core services (including Perl and mySQL).  The ePrints server will run as a normal user, and be accessed through a central proxy
-[[Image:Webserver_proxy.png:Proxied system install]]
+[[Image:Webserver_proxy.png]]
 ===Preparation===