Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add docker-compose instructions #24

Closed
jtpdowns opened this issue Feb 25, 2019 · 1 comment
Closed

Add docker-compose instructions #24

jtpdowns opened this issue Feb 25, 2019 · 1 comment
Labels
Neo4jExecutor Issues having to do with the Neo4jExecutor

Comments

@jtpdowns
Copy link
Contributor

If dotmotif were to be deployed in a Docker container, the default no-Neo4j-instance behavior would be to try to launch another container inside of the container. It would be good to describe the required steps to orchestrate an application container with a Neo4j container using docker-compose, which would allow you to network the two together and avoid the container-in-container problem.

@j6k4m8 j6k4m8 added the Neo4jExecutor Issues having to do with the Neo4jExecutor label Feb 26, 2019
@j6k4m8
Copy link
Member

j6k4m8 commented Jan 12, 2021

Big sigh of zero-github-issue relief: This is finally documented and explained in detail in the wiki.

And, incidentally: The pain-threshold for using the Neo4j executor is now way higher, since the GrandIsoExecutor bites way into the range of graph-sizes for which it used to make sense to switch to a graph database.

Woo! 🎉

@j6k4m8 j6k4m8 closed this as completed Jan 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Neo4jExecutor Issues having to do with the Neo4jExecutor
Projects
None yet
Development

No branches or pull requests

2 participants