Production Deployment¶
Important
This deployment is intended for production use. If you want to just test FIP Wizard locally, visit Local Deployment.
Requirements¶
Docker Engine version 19.03 (or higher)
Docker Compose version 1.25 (or higher)
Domain and DNS records set for providing FIP Wizard (you can use any other subdomains):
dsw.your-domain.tld
- for FIP Wizard (DSW)api.dsw.your-domain.tld
- for FIP Wizard API (DSW API)sparql.your-domain.tld
- for Triple Store (Nanopublications)
Setup¶
Get FIP Wizard¶
Download or git clone
repository https://github.com/fip-wizard/fip-deployment-production locally.
The folder fip-deployment-production
we call FIP Wizard root directory. It consists all necessary configuration files and docker-compose.yml
.
Configure domains and secrets¶
There are several things that you need to configure before running FIP Wizard for production deployment. In files, look for comments marked with (!)
:
server_name
andssl_certificate
values inproxy/nginx/agraph.conf
andproxy/nginx/dsw.conf
with your domain names. Those need to have valid DNS records pointing to that server.docker-compose.yml
-API_URL
(dsw_client
service) to your value forapi.dsw.your-domain.tld
dsw-server/application.yml
-clientUrl
to your value fordsw.your-domain.tld
, thensecret
,serviceToken
, andemail
section according to the comments thereallegrograph/agraph.cfg
- set strong password and optionally change username usingSuperUser
directive, the same credentials must be configured insubmission-service/config.yml
Obtain SSL certificates¶
Before providing FIP Wizard you need also to get SSL certificates to be able to use HTTPS. We recommend using Let’s Encrypt but you can use any other way and change Nginx proxy configuration accordingly.
Comment out
include
lines at the end ofproxy/nginx/nginx.conf
Start the proxy service
docker-compose up -d proxy
Get certificates for your domains:
sudo certbot certonly --webroot -w ./proxy/letsencrypt -d dsw.your-domain.tld
sudo certbot certonly --webroot -w ./proxy/letsencrypt -d api.dsw.your-domain.tld
sudo certbot certonly --webroot -w ./proxy/letsencrypt -d sparql.your-domain.tld
Create certificate file for AllegroGraph (it needs to merge
cert.pem
andprivkey.pem
obtained by Let’s Encrypt into a single file):
sudo cat /etc/letsencrypt/live/sparql.your-domain.tld/cert.pem /etc/letsencrypt/live/sparql.your-domain.tld/privkey.pem > ./allegrograph/cert.pem
Stop the proxy service
docker-compose down
Uncomment lines at the end of
proxy/nginx/nginx.conf
If getting certificates fails, it can be caused by incorrectly set DNS records. Optionally, verify if Nginx container is running and view its logs. You should also setup certificates renewal according to Certbot documentation.
First start¶
Start FIP Wizard (and wait a bit until all services start).
docker-compose up -d
Navigate to
dsw.your-domain.tld
, login usingalbert.einstein@example.com
with passwordpassword
and change default user accounts with strong passwords.In
sparql.your-domain.tld
, create a repositoryfip
in catalog/
and create other users with permissions according to your needs (see AllegroGraph documentation for details). For example, create an anonymous user with only read permissions to catalog / and repository fip.Restart FIP Wizard and wait a bit until all services start up (depending on your hardware, less than a minute).
docker-compose down
docker-compose up -d
Verify setup by creating FAIR Implementation Profile, saving it, creating a document, and submitting a nanopublication.
🎉 After this, your FIP Wizard is ready to be used!
To check if everything is working, you can use docker-compose logs
and docker-compose ps
commands.
⚙️ For additional configuration options, see Advanced Configuration.
Update¶
Stop FIP Wizard
Overwrite configurations and
docker-compose.yml
or simplygit pull
Check if there are new configuration values to be changed according to your setup (marked with
(!)
comments)Start FIP Wizard again
From root directory of fip-deployment-production
:
docker-compose down
git pull
docker-compose up -d
This may need you to git stash
your changes and then git stash pop
them (and eventually solve git conflicts).
Notes¶
For more information about docker-compose and its options, visit Docker documentation.
The main difference with respect to the Local Deployment is the adding Nginx proxy, certificates, and other additional security.