You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have set up PHPUnit tests so that Fuseki is installed by the init_fuseki.sh script as a regular Java process. If necessary, the script downloads the Fuseki installation tarball from the Apache Jena download site, starts it up, and then loads the test vocabulary data from the tests/test-vocab-data directory using the s-put utility that comes with Fuseki.
For Skosmos 3, I would like to switch to a dockerized Fuseki instance instead of using a regular Java process. This would have the following benefits:
The same Fuseki container (together with dockerized Skosmos, both running via docker compose) can also be used for running Cypress tests
We can use the exact same container setup both under GitHub Actions CI and local developer machines
"Eat your own dogfood": it's good practice to make use of our own Dockerfiles now that we have them
Prerequisites
We should first switch to the official Fuseki Dockerfile from Apache Jena; this is being worked on in PR #1477 by @kinow
How to implement
init_fuseki.sh needs to be rewritten so it simply runs a docker compose command instead of the current code for downloading, installing and starting up Fuseki; also, test vocabularies should be loaded using e.g. curl since we don't have s-put available anymore
some changes to the GitHub Actions CI configuration may be necessary
CONTRIBUTING.md and the wiki documentation for unit and integration tests should be modified accordingly (e.g. need to explain that Docker is necessary for running PHPUnit tests locally)
The text was updated successfully, but these errors were encountered:
Currently we have set up PHPUnit tests so that Fuseki is installed by the init_fuseki.sh script as a regular Java process. If necessary, the script downloads the Fuseki installation tarball from the Apache Jena download site, starts it up, and then loads the test vocabulary data from the
tests/test-vocab-data
directory using the s-put utility that comes with Fuseki.For Skosmos 3, I would like to switch to a dockerized Fuseki instance instead of using a regular Java process. This would have the following benefits:
Prerequisites
We should first switch to the official Fuseki Dockerfile from Apache Jena; this is being worked on in PR #1477 by @kinow
How to implement
docker compose
command instead of the current code for downloading, installing and starting up Fuseki; also, test vocabularies should be loaded using e.g.curl
since we don't haves-put
available anymoreThe text was updated successfully, but these errors were encountered: