uclalibrary / sinai-web Goto Github PK

Check the project out from GitHub, package it and start it.

git clone https://github.com/UCLALibrary/sinai-web
cd sinai-web
mvn clean package
target/startup.sh --env <dev|test|stage|prod>

The --env argument allows for selection of the Solr core and IIIF image server to connect to:

It generates a self-signed certificate, so when you visit

https://localhost:8443/

You will have to click through the security warning.

Check out the Library's restricted access 'ansible' project and run:

git clone https://github.com/UCLALibrary/ansible
cd ansible
PLAYBOOK=sinai_scholars_stage vagrant up

This also generates a self-signed certificate, so when you visit

https://localhost/

You will have to click through the security warning.

You can build the project with support for connecting a JDWP agent by running with:

mvn clean install -Ddev.tools=JDWP_AGENTLIB

Or with support for a JMX monitor:

mvn clean install -Ddev.tools=JMX_REMOTE

Or with both:

mvn clean install -Ddev.tools="JDWP_AGENTLIB JMX_REMOTE"

You can also supply the dev.tools variable in a default Maven profile. See src/main/resources/settings.xml for an example.

The Sinai Scholar's site uses Mirador as its image viewer. We are maintaining a fork here. The build output of the code on the develop-prod branch of that repository is included in this repository (sinai-web) by the following process:

SINAI_PATH=/path/to/sinai-web
SINAI_MIRADOR_PATH=${SINAI_PATH}/src/main/webapp/mirador

git clone https://github.com/UCLALibrary/mirador
cd mirador
git checkout -b develop-prod origin/develop-prod
grunt && grunt uglify

rm -rf ${SINAI_MIRADOR_PATH}
cp -r ./mirador ${SINAI_MIRADOR_PATH}

If you want to login with the new EMEL auth system and a DDNS service, you can supply the Sinai host variable at the point of running the test startup script; for instance:

SINAI_HOST=lisforge.ddns.net target/startup.sh

This is probably only relevant to developers testing the system using an allowed domain name. When supplying the host in this fashion, it's assumed the service is running at port 443 rather than at the out of the box testing default, 8443.

Contact Kevin or Mark with any build, etc., questions you have.