Closed kevinschaper closed 1 year ago
@kevinschaper, I'm generally comfortable with the task itself in terms of my knowledge (AWS, docker, neo4j, kg's, Monarch, etc.).
I'll want to better understand where this particular artifact/resource sits within the wider Monarch QC / publication landscape. Perhaps we can briefly summarize the specific rationale and characteristics the resource has and/or needs to serve: target use cases, intended users, intended life cycle of maintenance: schedule of push/pull (with Monarch data); notifications to users, etc.
Maybe I'm overly complicating things... but just clarifying customer acceptance of the solution.
The code resolving this issue was moved out of Monarch Ingest and into a new (standalone) repository at https://github.com/monarch-initiative/monarch-neo4j
We need to convert the un-dockerized neo4j 3.4 on scigraph.ncats.io to something that's easier to manage.
@falquaddoomi was super helpful in suggesting a docker compose config config & shell script as a starting place:
docker-compose.yml
load_and_boot.sh