set up dedicated ECHOLOT NeoWiki instance

[vronk]

There is NeoWiki dev instance already:
https://neowiki.dev/

Wonder if we may want a separate one dedicated for experiments within ECHOLOT.

@JeroenDeDauw, opinion?

[JeroenDeDauw]

If it's helpful to anyone, then go for it. No objections from our side. NeoWiki is ready for this. Installation instructions are at https://neowiki.ai/docs/operations/installation.

The one thing that comes to mind is that if the software is updated slowly, the additional instance might confuse people. Imagine we announce RDF export is live and want people to try it, while this new instance is running a month-old NeoWiki that doesn't have it.

Let us (inc @malberts @alistair3149) know if there are issues during setup.

[vronk]

sorry for the slow reaction.
I understood that the demo instance is being flushed and repopulated regularly.
I think it is important for the test instance to have (control over) the persistence.

[malberts]

The demo instance resets the demo data included in the NeoWiki extension. We do not currently remove additional subjects created outside of that, so you can keep your own dedicated test data on the demo instance too.

If you want to control when the core demo data reset happens, it makes sense to have your own instance. Just keep in mind the same script that updates that demo data would reset it on your instance too, so it's not possible to have the latest core demo data and keep modifications to that data. For your own additional test data it is fine either way.

[JeroenDeDauw]

@vronk we often manually run make import-demo-data. You have access to all the tooling already. If you want to fully remove your wikis data, you can run make remove && make demo (that drops the container volumes with the db and graphs)