Hi David,
In Arches 5.0, ontologies are loaded as part of a package. See
https://github.com/archesproject/arches-her/tree/master/arches_her/pkg for
an example of how ontologies are defined. These are automatically loaded
as part of the package load command.
Hope this helps.
-Dennis
On
Hi Ben
Thanks, that was it: starting the elasticsearch and db containers first was
the solution.
My docker-compose file asked for the default resource models and concepts.
Although the concepts loaded ok, the branches and models didn't, with a
missing ontology, although I can't see how to
Im going to guess that the elasticsearch container is not ready and the
migration script fails when it attempts to run the first time through and
Arches ends up in a bad state which it generally can never recover from.
docker-compose down -v
This will kill and delete all the badly formed docker
Thanks, Ben: your comment helped me make some progress (to another error ;-)
The problem is that the Readme.md in the docker directory of the Github
archesproject/arches repo (file last revised 17 months ago!) is inaccurate
or vague when it says "Create a new folder for your custom Arches code"
Hi,
I think the key error is on line 63 of the gist you posted. For some
reason, it is interpreting file bind mount as a directory and not as a
file. If I run the default docker compose file here, and start up the db
container, this is the log output I get:
$ docker logs db
Add rule to pg_hba:
I need a new Arches installation to develop some stuff for a conference
presentation, so I thought I'd take the opportunity to not only use the
latest version but also run it under Docker.
Following the instructions at
https://github.com/archesproject/arches/blob/master/docker/Readme.md, I got
