Spin up the service
Full list of steps to perform before spinning up the service:
Extract the Terminology Server release archive to a folder. E.g.
/opt/snow-owl
(Optional) Obtain an SSL certificate
Make sure a DNS A record is routed to the host's public IP address
Go into the folder
./snow-owl/docker/cert
Execute the
./init-certificate.sh
script:
./init-certificate.sh -d snow-owl.example.com
(Optional) Configure access for managed Elasticsearch Cluster (elastic.co)
(Optional) Extract dataset to
./snow-owl/resources
where folder structure should look like./snow-owl/resources/indexes/nodes/0
at the end.Verify file ownership to be UID=1000 and GID=0:
chmod -R 1000:0 ./snow-owl/docker ./snow-owl/logs ./snow-owl/resources
Check any credentials or settings that need to be changed in
./snow-owl/docker/.env
Authenticate with our private docker registry while in the folder
./snow-owl/docker
:cat docker_login.txt | docker login -u <username> --password-stdin https://docker.b2ihealthcare.com
Issue a pull (in folder
./snow-owl/docker
)docker compose pull
Spin up the service (in the folder
./snow-owl/docker
)docker compose up -d
Verify that the REST API of the Terminology Server is available at:
With SSL:
https://snow-owl.example.com/snowowl
Without SSL:
http://hostname:8080/snowowl
Verify that the server and cluster status is GREEN by querying the following REST API endpoint:
With SSL:
curl https://snow-owl.example.com/snowowl/info
Without SSL:
curl http://hostname:8080/snowowl/info
Enjoy using the Snow Owl Terminology Server 🎉
Last updated