Currently, our data dumping to Neo4j is built and run using individual docker commands. This makes it difficult to manage dependencies and configurations, and can lead to inconsistencies between development and production environments.
Proposed Solution
I propose using a docker-compose.yaml file to manage the dependencies and configurations of our data dumping into Neo4j. This will allow us to easily spin up and down the entire pipeline with a single command docker-compose up and docker-compose down respectively, and ensure consistency between development and production environments.
Benefits
Easy management of dependencies and configurations
Consistency between development and production environments
Description
Currently, our data dumping to Neo4j is built and run using individual docker commands. This makes it difficult to manage dependencies and configurations, and can lead to inconsistencies between development and production environments.
Proposed Solution
I propose using a
docker-compose.yamlfile to manage the dependencies and configurations of our data dumping into Neo4j. This will allow us to easily spin up and down the entire pipeline with a single commanddocker-compose upanddocker-compose downrespectively, and ensure consistency between development and production environments.Benefits