Could we change the README instructions to a more step-by-step way to instantiate neo4j?
The version of neo4j should 4.4. not 4.1 as in the current command.
It might be good to have a slightly more iterative way, instead of a single step. If something goes wrong it can help.
Something like that:
Copy the dump file to neo4j/dumps
cp sourcedata_v2-0-2.db.dump.2023-09-25-08.45.40 neo4j/dumps/
Run a standalone neo4j 4.4 container with appropriate volume bindings:
docker run --rm --name neo4j-load \
--env-file .env \
--mount type=bind,source=$PWD/neo4j/data,target=/data \
--mount type=bind,source=$PWD/neo4j/dumps,target=/dumps \
-it neo4j:4.4 bash # note the version here is 4.4!Sanity checks within the container to see if the dumps file is there:
Load the database with neo4j-admin:
neo4j-admin load --database=neo4j \
--from=/dumps/sourcedata_v2-0-2.db.dump.2023-09-25-08.45.40 \
--forceLeave the container
Could we change the README instructions to a more step-by-step way to instantiate neo4j?
The version of neo4j should 4.4. not 4.1 as in the current command.
It might be good to have a slightly more iterative way, instead of a single step. If something goes wrong it can help.
Something like that:
Copy the dump file to
neo4j/dumpsRun a standalone neo4j 4.4 container with appropriate volume bindings:
docker run --rm --name neo4j-load \ --env-file .env \ --mount type=bind,source=$PWD/neo4j/data,target=/data \ --mount type=bind,source=$PWD/neo4j/dumps,target=/dumps \ -it neo4j:4.4 bash # note the version here is 4.4!Sanity checks within the container to see if the dumps file is there:
Load the database with neo4j-admin:
neo4j-admin load --database=neo4j \ --from=/dumps/sourcedata_v2-0-2.db.dump.2023-09-25-08.45.40 \ --forceLeave the container
exit