In the end, I used another approach and installed multiple Neo4J databases on our one and only Edgeryders server. So we have now, in total:
-
graphryder1.edgeryders.eu: NGI Forward dataset, on the Edgeryders server
-
graphryder2.edgeryders.eu: OpenCare dataset, on Hugi’s Digital Ocean VPS
-
graphryder3.edgeryders.eu: POPREBEL dataset, on the Edgeryders server
This setup is now considered “Graphryder Interactive Dashboard v1” (a deliverable, see the plan). There are still things to tidy up internally to finalize this tooling. After that, we’ll have everything Graphryder under a single domain graphryder.edgeryders.eu, using one codebase for Graphryder API and Dashboard on the file system together with multiple configuration files.
Ideally I’ll also add a little command line tool that automates the setup of a new Graphryder website and Neo4J database for a new dataset:
graphryder-cli create --tag ethno-earthos --name earthos
For the short term incl. new projects, that will be good to go as setting up Graphryder is then just one command on the server. We can then focus on a medium to longer term solution …
(Also @alberto and @amelia: your Graphryder installation for POPREBEL is ready, see above. The details view is still broken, but will be fixed in the next days …)