• bash shell 4.x. It should be included by default on Linux. On Windows you can install theWindows Subsystem for Linux.
• openssl available on$PATH
• Docker installed. At least 8GB of memory dedicated to Docker is recommended.
• Docker Compose installed

1. Fork this repository and clone the fork into a folder
2. 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=httpsHTTP_PORT=81HTTPS_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

3. Setup server's SSL certificates by running this from command line:

   ./bin/server-cert-gen.sh .env nginx ssl

   The script will create anssl sub-folder where the SSL certificates and/or public keys will be placed.
4. Create the following secrets with certificate/truststore passwords:
   • secrets/client_truststore_password.txt
   • secrets/owner_cert_password.txt
   • secrets/secretary_cert_password.txtThe one you will need to remember in order to authenticate with LinkedDataHub using WebID client certificate isowner_cert_password.
5. Launch the application services by running this from command line:

   docker-compose up --build

   It will build LinkedDataHub's Docker image, start its container and mount the following sub-folders:
   • ssl
     • owner stores root owner's WebID certificate, keystore, and public key
     • secretary stores root application's WebID certificate, keystore, and public key
     • server stores the server's certificate (also used by nginx)
   • data where the triplestore(s) will persist RDF data
   • datasets where LDH persists agent metadata files
   • uploads where LDH stores content-hashed file uploadsIt should take up to half a minute as datasets are being loaded into triplestores. After a successful startup you should see periodic healtcheck requests being made to thehttps://localhost:4443/ns URL.
6. Installssl/owner/keystore.p12 into a web browser of your choice (password is theowner_cert_password secret value)
   • 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 (drag it to thelocal section).
   • Microsoft Edge: Does not support certificate management, you need to install the file into Windows.Read more here.
7. For authenticated API access use thessl/owner/cert.pem HTTPS client certificate.If you are running Linux with user other thanroot, you might need to fix the certificate permissions because Docker bind mounts are owned byroot by default. For example:

   sudo setfacl -m u:$(whoami):r ./ssl/owner/*

8. Openhttps://localhost:4443/ in the web browser or usecurl for API access, for example:

   curl -k -E ./ssl/owner/cert.pem:<your cert password> -H"Accept: text/turtle"'https://localhost:4443/'

• There might go up to a minute before the web server is available because the nginx server depends on healthy LinkedDataHub and the healthcheck is done every 20s
• 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

A 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.

Secrets used indocker-compose.yml:

owner_cert_password

Password of the owner's WebID certificate

secretary_cert_password

Password of the secretary's WebID certificate

client_truststore_password

Password of the client truststore

google_client_id

Google's OAuth client ID

Login with Google authentication is enabled when this value is provided

google_client_secret

Google's OAuth client secret

LinkedDataHub supports a range of configuration options that can be passed as environment parameters indocker-compose.yml. The most common ones are:

CATALINA_OPTS

Tomcat'scommand line options

SELF_SIGNED_CERT

true if the server certificate is self-signed

SIGN_UP_CERT_VALIDITY

Validity of the WebID certificates of signed up users (not the owner's)

IMPORT_KEEPALIVE

The period for which the data import can keep an open HTTP connection before it times out, in ms. The larger files are being imported, the longer it has to be in order for the import to complete.

MAX_CONTENT_LENGTH

Maximum allowed size of the request body, in bytes

MAIL_SMTP_HOST

Hostname of the mail server

MAIL_SMTP_PORT

Port number of the mail server

The options are described in more detail in theconfiguration documentation.

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 uploads&& docker-compose down -v

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