The AS application is self-contained, but you do need a JVM. I think a JRE is sufficient, but we've used the full OpenJDK for deploying. The AS docs specify version 1.8 for your java.
cd /vhosts/ && wget https://github.com/archivesspace/archivesspace/releases/download/v3.0.1/archivesspace-v3.0.1.zipunzip archivesspace-v3.0.1.zip
For anything other than local fun, use a robust SQL ("squill") database. See the official readme for different info. Note that the following steps assume that you have already downloaded and unpacked the ArchivesSpace release from github.
- Grab the appropriate java connector lib for your database (mysql = mysql-connector-java-${version-to-match-your-mysql}.jar; mariadb = connector-java-2.7.3.jar) and drop it in to
${as-root-dir}/lib/. - Set up your database:
- create your database and be sure to use UTF-8 as the default character encoding.
- create your user and grant them all privileges on the new database.
- Modify the ArchivesSpace config file (
${as-root-dir}/config/config.rb) and update theAppConfig[:db_url]line to use the credentials you just set on the database. - Change directory to
${as-root-dir}/scriptsand runsetup-database.shto get the new database configured for use by the application. - Head over to the "Getting Started" section to give the application a test start.
Notes and/or Warnings:
- During the first startup, start ArchivesSpace as a daemon:
cd to ${as-root-dir}andarchivesspace.sh start - Tail the log, in
${as-root-dir}/logs/archivesspace.out, and watch for trouble messages.