Quickstart:Install EPrints - Revision history

Ap1e26 at 10:54, 7 October 2026

2026-10-07T10:54:56Z

2026-10-07T10:53:30Z

‎Database Tables and Website

2026-10-07T10:53:16Z

‎Creating the Database Tables and Website

2026-10-07T10:52:39Z

‎Note:

2026-10-07T10:51:56Z

‎Creating the Archive

2026-10-07T10:48:41Z

‎Change directory to the eprints directory

2026-10-07T10:48:29Z

‎Change directory to the eprints directory

2026-10-07T10:48:11Z

‎Creating the Archive

2026-10-07T10:40:52Z

2026-10-07T10:39:29Z

← Older revision		Revision as of 10:54, 7 October 2026
Line 49:		Line 49:
	== Database Tables and Website ==		== Database Tables and Website ==
	These have now been created when you created the archive.		These have now been created when you created the archive.
		+
		+	== Next Steps ==
		+	You are now ready to configure the EPrints system! Go to the [[Quickstart:Install EPrints \| next page of this guide]] to find out how.

@@ Line 47: / Line 47: @@
 <i>If you don't want a research publications archive, in the above command use <code>zero</code> instead of <code>pub</code>. This will create a very basic repository, which can either store very generic items or can be more greatly customised as it does not have some of the intentional restrictions that come with a Research Publications repository.  Other flavours of repository may be available but these will have to have be added their <tt>FLAVOUR_lib</tt> to the <tt>EPRINTS_PATH/flavours/</tt> directory.  If you run just <code>bin/epadmin create</code> without a further parameter or one that is not recognised, the command should suggest what types (flavours) of repository archive are available.</i>
-=== Database Tables and Website ===
+== Database Tables and Website ==
 These have now been created when you created the archive.

@@ Line 47: / Line 47: @@
 <i>If you don't want a research publications archive, in the above command use <code>zero</code> instead of <code>pub</code>. This will create a very basic repository, which can either store very generic items or can be more greatly customised as it does not have some of the intentional restrictions that come with a Research Publications repository.  Other flavours of repository may be available but these will have to have be added their <tt>FLAVOUR_lib</tt> to the <tt>EPRINTS_PATH/flavours/</tt> directory.  If you run just <code>bin/epadmin create</code> without a further parameter or one that is not recognised, the command should suggest what types (flavours) of repository archive are available.</i>
-===Creating the Database Tables and Website ===
+=== Database Tables and Website ===
-These will have been created when you created the archive.
+These have now been created when you created the archive.

@@ Line 44: / Line 44: @@
 <code>bin/epadmin create pub</code>
-===== <i>Note:</i> =====
+===== <i>Note on Archive Flavour</i> =====
 <i>If you don't want a research publications archive, in the above command use <code>zero</code> instead of <code>pub</code>. This will create a very basic repository, which can either store very generic items or can be more greatly customised as it does not have some of the intentional restrictions that come with a Research Publications repository.  Other flavours of repository may be available but these will have to have be added their <tt>FLAVOUR_lib</tt> to the <tt>EPRINTS_PATH/flavours/</tt> directory.  If you run just <code>bin/epadmin create</code> without a further parameter or one that is not recognised, the command should suggest what types (flavours) of repository archive are available.</i>
 ===Creating the Database Tables and Website ===
 These will have been created when you created the archive.

@@ Line 44: / Line 44: @@
 <code>bin/epadmin create pub</code>
-If you don't want a research publications archive, in the above command use <code>zero</code> instead of <code>pub</code>. This will create a very basic repository, which can either store very generic items or can be more greatly customised as it does not have some of the intentional restrictions that come with a Research Publications repository.  Other flavours of repository may be available but these will have to have be added their <tt>FLAVOUR_lib</tt> to the <tt>EPRINTS_PATH/flavours/</tt> directory.  If you run just <code>bin/epadmin create</code> without a further parameter or one that is not recognised, the command should suggest what types (flavours) of repository archive are available.
+===== <i>Note:</i> =====
 ===Creating the Database Tables and Website ===
 These will have been created when you created the archive.

@@ Line 36: / Line 36: @@
 <br/>
 ==== Change directory to the eprints directory ====
-<i>(<tt>/opt/eprints3</tt> by default)</i>
+<i>(<tt>/opt/eprints3</tt> by default)</i><br/>
 <code>cd /opt/eprints3</code>
 <br/>

@@ Line 26: / Line 26: @@
 ==Creating the Archive==
-<p>Make sure the database is actually running.</p>
+==== Make sure the database is actually running ====
 <p>MySQL:</p>
 <code>sudo systemctl status mysql</code>
 <p>MariaDB:</p>
 <code>sudo systemctl status mariadb</code>
 <br/>
-<p>Change to your "eprints" user.</p>
+==== Change to your "eprints" user ====
 <code>su eprints</code>
 <br/>
-<p>Change directory to the eprints directory (<tt>/opt/eprints3</tt> by default)</p>
+==== Change directory to the eprints directory ====
 <code>cd /opt/eprints3</code>
 <br/>
-<p>Then create a research publications archive. (You will be prompted to answer various questions about the configuration of your archive):</p>
+==== Create a research publications archive ====
 <code>bin/epadmin create pub</code>