-
Notifications
You must be signed in to change notification settings - Fork 46
Installation
-
Check that you have Java 7 or 8 (sometimes referred to also as '1.7' and '1.8') and a Java Development Kit (JDK) on your machine (e.g. following both 'Option 1' and 'Option 2' procedures that are explained here, including the final step related to javac). If not, download and install the JDK from http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html.
-
Get the EFES software: either download the ZIP from https://github.com/EpiDoc/EFES/archive/master.zip or clone from Github (or from your own fork of the repository) if you have an account already.
-
If you downloaded the ZIP file, unzip it in a directory of your choosing (e.g. on your Desktop), changing the folder name from 'EFES-master' to 'EFES'. See below on including EpiDoc Stylesheets in your EFES install.
-
Open up your Command prompt/Terminal:
- Windows: in the search box in the Start menu type: cmd
- GNU/Linux or Mac OS X: in the search box in the Menu bar on top type: terminal
-
Start the EFES build process, navigating to your EFES folder (a) and then running a script that will start Jetty, a lightweight web server that is pre-configured to run all EFES components (b):
-
Windows:
- navigate to your EFES folder typing the following command and then pressing Enter: cd Desktop\EFES
- type the following command and then press Enter: build.bat
-
GNU/Linux or Mac OS X:
- navigate to your EFES folder typing the following command and then pressing Enter: cd Desktop/EFES
- type the following command and then press Enter: sh build.sh
-
At this point, many messages will appear in the Terminal, among which "Development server is running at http://127.0.0.1:9999/".
- Visit http://127.0.0.1:9999/ with your web browser. You’ll see a “Welcome to EFES” page (NB: be patient, since it can take dozens of seconds for server initialisation to complete)
- Congratulations! EFES is now all set up. You can start filling in your content. Remember to keep Jetty running on your Terminal/Command Line while working on EFES. To stop EFES: either type Ctrl+C in the Terminal or close it.
- In your file navigator navigate to /webapps/ROOT/content/xml/epidoc/. This is where you will put your EpiDoc XML files. When you first install EFES, this folder will contain several sample EpiDoc files to help you start off. (NB: to be able to see the files, you will need to create an RDF repository first)
- If you have cloned EFES using GitHub Desktop
- Do nothing. The stylesheets will already have been cloned into
webapps/ROOT/kiln/stylesheets/epidoc
for you from the submodule
- Do nothing. The stylesheets will already have been cloned into
- If you have cloned EFES using Git from the commandline/terminal/bash:
- Navigate into the EFES folder, and type the command
git submodule update --init
. This will clone the submodule for you as per (1) above.
- Navigate into the EFES folder, and type the command
- If you have downloaded a static version of EFES as a ZIP from Github:
- Download the ZIP of the EpiDoc Stylesheers from https://github.com/EpiDoc/Stylesheets/, extract the ZIP archive into a new folder, and copy the contents of this folder into
webapps/ROOT/kiln/stylesheets/epidoc
in your EFES instance.
- Download the ZIP of the EpiDoc Stylesheers from https://github.com/EpiDoc/Stylesheets/, extract the ZIP archive into a new folder, and copy the contents of this folder into
- The command cd ... above will work only if the 'EFES' folder has been saved directly on your Desktop (and not, e.g., inside another folder on your Desktop); if the folder has been saved in a different position, in the command above replace "Desktop" with the actual path of the EFES folder.
- If the Terminal returns error messages concerning authorisation problems, type the following command in the Terminal and then press Enter: chmod +x build.sh
- If the Terminal returns error messages concerning Java, go back to step 1 and ensure that you have installed the correct Java/JDK version.
- Sometimes to apply changes it is needed to emtpy the browser cache, or to stop and restart EFES from the Terminal.