1. Have yourbash shell ready. It should be included by default on Linux. On Windows you can install theWindows Subsystem for Linux.
2. Install Docker
   • Install Docker Compose, if it is not already included in the Docker installation
3. Fork this repository and clone the fork into a folder
4. In the folder, create an.env file and fill out the missing values (you can use.env_sample as a template). For example:

   COMPOSE_CONVERT_WINDOWS_PATHS=1COMPOSE_PROJECT_NAME=linkeddatahubPROTOCOL=httpsPROXY_HTTP_PORT=81PROXY_HTTPS_PORT=4443HOST=localhostABS_PATH=/OWNER_MBOX=john@doe.comOWNER_GIVEN_NAME=JohnOWNER_FAMILY_NAME=DoeOWNER_ORG_UNIT=My unitOWNER_ORGANIZATION=My orgOWNER_LOCALITY=CopenhagenOWNER_STATE_OR_PROVINCE=DenmarkOWNER_COUNTRY_NAME=DK

5. Setup SSL certificates/keys by running this from command line (replace$owner_cert_pwd and$secretary_cert_pwd with your own passwords):

   ./scripts/setup.sh .env ssl $owner_cert_pwd $secretary_cert_pwd 3650

   The script will create anssl sub-folder where the SSL certificates and/or public keys will be placed. It requires Java'skeytool as well asopenssl to be available on$PATH.
6. Launch the application services by running this from command line:

   docker-compose up

   LinkedDataHub will start and mount the following sub-folders:
   • data where the triplestore(s) will persist RDF data
   • uploads where LDH stores content-hashed file uploadsThe first should take around half a minute as datasets are being loaded into triplestores. After a successful startup, the last line of the Docker log should read something like:

   linkeddatahub_1     | 09-Feb-2021 14:18:10.536 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [32609] milliseconds

7. Installssl/owner/keystore.p12 into a web browser of your choice (password is the$owner_cert_pwd value supplied tosetup.sh)
   • Google Chrome:Settings > Advanced > Manage Certificates > Import...
   • Mozilla Firefox:Options > Privacy > Security > View Certificates... > Import...
   • Apple Safari: The file is installed directly into the operating system. Open the file and import it using theKeychain Access tool.
   • Microsoft Edge: Does not support certificate management, you need to install the file into Windows.Read more here.
8. Openhttps://localhost:4443/ in that web browser

• You will likely get a browser warning such asYour connection is not private in Chrome orWarning: Potential Security Risk Ahead in Firefox due to the self-signed server certificate. Ignore it: clickAdvanced andProceed orAccept the risk to proceed.
  • If this option does not appear in Chrome (as observed on some MacOS), you can openchrome://flags/#allow-insecure-localhost, switchAllow invalid certificates for resources loaded from localhost toEnabled and restart Chrome
• .env_sample and.env files might be invisible in MacOS Finder which hides filenames starting with a dot. You should be able tocreate it using Terminal however.
• On Linux your user may need to be a member of thedocker group. Add it using

sudo usermod -aG docker ${USER}

and re-login with your user. An alternative, but not recommended, is to run

sudo docker-compose up

Besides owner WebID configuration, the most common case is changing the base URI from the defaulthttps://localhost:4443/ to your own.

Lets usehttps://ec2-54-235-229-141.compute-1.amazonaws.com/linkeddatahub/ as an example. We need to split the URI into components and set them in the.env file using the following parameters:

PROTOCOL=httpsHTTP_PORT=80HTTPS_PORT=443HOST=ec2-54-235-229-141.compute-1.amazonaws.comABS_PATH=/linkeddatahub/

ABS_PATH is required, even if it's just/.

Dataspaces are configured inconfig/system.trig. Relative URIs will be resolved against the base URI configured in the.env file.

⚠️ Do not use blank nodes to identify applications or services. We recommend using theurn: URI scheme, since LinkedDataHub application resources are not accessible under their own dataspace.

If you need to start fresh and wipe the existing setup (e.g. after configuring a new base URI), you can do that using

sudo rm -rf data && docker-compose down -v

⚠️ This willremove the persisted data as well as Docker volumes.