We need all steps documented from start to finish (including log into X, call Y, etc) that are required to restart OLS.

We should try to do a test deployment of OLS 4 on the semanticly servers. This has medium priority, but I think @anitacaron you could do this at some point in between major issues.

git clone https://github.com/EBISPOT/ols4.git
cd ols4
export OLS4_CONFIG=./dataload/configs/efo.json
docker compose up

for a custom ontology you can make a new config in the same folder as efo.json using efo.json as a template. The testcases folder is mounted in docker, so you can copy your owl file there. For HP international I use
"ontology_purl": "file:///opt/dataload/testcases/hpi.owl",

in the json, where hpi.owl is in testcases/

then I just export OLS4_CONFIG=./dataload/configs/hpi.json and docker compose up

Currently, I dont know how to do this. I do not want any large series of ssh commands and some manual scripts to do this, there should be a nice, easy way to trigger a rebuild after an updated config and redeploy. Maybe even an automatic one when the config is changed?

@mellybelly would like to ensure that people can quickly check a term they encounter in the UI on an official Monarch OLS instance (a production, rather than the current developer instance we have at http://ols.monarchinitiative.org/ontologies).

I think we first need #5 and then make a ticket for adding a second instance.

However I recommend to wait until OLS4 is more done. It get better by the day, and the current OLS3 cannot handle PHENIO at all.