These instructions are purposefully opinionated and terse to help you get your development environment up and running as quickly as possible! Please note that familiarity with running commands from the terminal is assumed.
Contents:
The quickest way to get Dataverse running is to use Vagrant as described in the Tools section, but for day to day development work, we recommended the following setup.
Mac OS X or Linux is required because the setup scripts assume the presence of standard Unix utilities.
Windows is not well supported, unfortunately, but Vagrant and Minishift environments are described in the Windows Development section.
Dataverse requires Java 8.
We suggest downloading OpenJDK from https://adoptopenjdk.net
On Linux, you are welcome to use the OpenJDK available from package managers.
NetBeans IDE is recommended, and can be downloaded from http://netbeans.org . Developers may use any editor or IDE. We recommend NetBeans because it is free, works cross platform, has good support for Jakarta EE projects, and includes a required build tool, Maven.
Below we describe how to build the Dataverse war file with Netbeans but if you prefer to use only Maven, you can find installation instructions in the Tools section.
On Mac, install Homebrew to simplify the steps below: https://brew.sh
Fork https://github.com/IQSS/dataverse and then clone your fork like this:
git clone git@github.com:[YOUR GITHUB USERNAME]/dataverse.git
If you installed Netbeans, follow these steps:
If you installed Maven instead of Netbeans, run mvn package. Check for “BUILD SUCCESS” at the end.
NOTE: Do you use a locale different than en_US.UTF-8 on your development machine? Are you in a different timezone
than Harvard (Eastern Time)? You might experience issues while running tests that were written with these settings
in mind. The Maven pom.xml tries to handle this for you by setting the locale to en_US.UTF-8 and timezone
UTC, but more, not yet discovered building or testing problems might lurk in the shadows.
On Mac, run this command:
brew install jq
On Linux, install jq from your package manager or download a binary from http://stedolan.github.io/jq/
Payara 5.201 or higher is required.
To install Payara, run the following commands:
cd /usr/local
sudo curl -O -L https://s3-eu-west-1.amazonaws.com/payara.fish/Payara+Downloads/5.2020.6/payara-5.2020.6.zip
sudo unzip payara-5.2020.6.zip
sudo chown -R $USER /usr/local/payara5
PostgreSQL 9.6 is recommended to match the version in the Installation Guide.
On Mac, go to https://www.postgresql.org/download/macosx/ and choose “Interactive installer by EDB” option. We’ve tested version 9.6.19. When prompted to set a password for the “database superuser (postgres)” just enter “password”.
After installation is complete, make a backup of the pg_hba.conf file like this:
sudo cp /Library/PostgreSQL/9.6/data/pg_hba.conf /Library/PostgreSQL/9.6/data/pg_hba.conf.orig
Then edit pg_hba.conf with an editor such as vi:
sudo vi /Library/PostgreSQL/9.6/data/pg_hba.conf
In the “METHOD” column, change all instances of “md5” to “trust”. This will make it so PostgreSQL doesn’t require a password.
In the Finder, click “Applications” then “PostgreSQL 9.6” and launch the “Reload Configuration” app. Click “OK” after you see “server signaled”.
Next, to confirm the edit worked, launch the “pgAdmin” application from the same folder. Under “Browser”, expand “Servers” and double click “PostgreSQL 9.6”. When you are prompted for a password, leave it blank and click “OK”. If you have successfully edited “pg_hba.conf”, you can get in without a password.
On Linux, you should just install PostgreSQL from your package manager without worrying about the version as long as it’s 9.x. Find pg_hba.conf and set the authentication method to “trust” and restart PostgreSQL.
Solr 7.7.2 is required.
To install Solr, execute the following commands:
sudo mkdir /usr/local/solr
sudo chown $USER /usr/local/solr
cd /usr/local/solr
curl -O http://archive.apache.org/dist/lucene/solr/7.7.2/solr-7.7.2.tgz
tar xvfz solr-7.7.2.tgz
cd solr-7.7.2/server/solr
cp -r configsets/_default collection1
curl -O https://raw.githubusercontent.com/IQSS/dataverse/develop/conf/solr/7.7.2/schema.xml
curl -O https://raw.githubusercontent.com/IQSS/dataverse/develop/conf/solr/7.7.2/schema_dv_mdb_fields.xml
curl -O https://raw.githubusercontent.com/IQSS/dataverse/develop/conf/solr/7.7.2/schema_dv_mdb_copies.xml
mv schema*.xml collection1/conf
curl -O https://raw.githubusercontent.com/IQSS/dataverse/develop/conf/solr/7.7.2/solrconfig.xml
mv solrconfig.xml collection1/conf/solrconfig.xml
cd /usr/local/solr/solr-7.7.2
(Please note that the extra jetty argument below is a security measure to limit connections to Solr to only your computer. For extra security, run a firewall.)
bin/solr start -j "-Djetty.host=127.0.0.1"
bin/solr create_core -c collection1 -d server/solr/collection1/conf
Navigate to the directory where you cloned the Dataverse git repo change directories to the scripts/installer directory like this:
cd scripts/installer
Create a Python virtual environment, activate it, then install dependencies:
python3 -m venv venv
source venv/bin/activate
pip install psycopg2-binary
The installer will try to connect to the SMTP server you tell it to use. If you don’t have a mail server handy you can run nc -l 25 in another terminal and choose “localhost” (the default) to get past this check.
Finally, run the installer (see also README_python.txt if necessary):
python3 install.py
After the script has finished, you should be able to log into Dataverse with the following credentials:
Run the following command:
curl http://localhost:8080/api/admin/settings/:DoiProvider -X PUT -d FAKE
This will disable DOI registration by using a fake (in-code) DOI provider. Please note that this feature is only available in version >= 4.10 and that at present, the UI will give no indication that the DOIs thus minted are fake.
If you can log in to Dataverse, great! If not, please see the Troubleshooting section. For further assitance, please see “Getting Help” in the Introduction section.
You’re almost ready to start hacking on code. Now that the installer script has you up and running, you need to continue on to the Tips section to get set up to deploy code from your IDE or the command line.
Previous: Introduction | Next: Tips