These are some brief instructions to get you up and running with Ontoserver.
The requirements for running an Ontoserver instance are heavily dependent on the intended usage. For the basic usage pattern (< 20 concurrent users, syndicating a small number of binary indexes but not building indexes from source), the following resource levels are recommended (on top of a 64-bit docker machine)
Resource | Minimum | Recommended |
CPUs or Cores | 2 | 4 |
RAM | 4GB | 12GB |
Storage/Disk | 10GB | 20GB |
Building indexes from sources (e.g. RF2) is very demanding on memory - in these cases, at least 12GB of RAM is recommended.
In order to run Ontoserver, you first need a Docker Machine. This will allow you to control the hosts (whether real or virtual, local or remote) on which Ontoserver and its database will run.
The simplest method is to download and install Docker Toolbox https://www.docker.com/products/docker-toolbox
This should provide you with both the docker and docker-compose commands.
If you wish to run Ontoserver on a remote virtual host, you may need to configure the appropriate drivers
docker login
version: '2' volumes: onto: driver: local pgdata: driver: local services: db: image: postgres volumes: - pgdata:/var/lib/postgresql/data ontoserver: image: aehrc/ontoserver:ctsa-4.1 container_name: ontoserver depends_on: - db ports: - "8443:8443" - "8080:8080" environment: - authentication.oauth.endpoint.client_id.0=NCTS_ACCESS_CODE - authentication.oauth.endpoint.client_secret.0=NCTS_CLIENT_SECRET volumes: - onto:/var/onto
docker-compose up -d
Note: Ontoserver can take a short while (up to 60 seconds) to start up. During this time it will not respond to requests such as downloading an SCT-AU version.