Skip to content
This repository was archived by the owner on Jul 10, 2023. It is now read-only.

Migrate from mongodb-tools to christkv/mongodb-topology-manager #54

Closed
3 tasks
imlucas opened this issue Mar 3, 2016 · 2 comments
Closed
3 tasks

Migrate from mongodb-tools to christkv/mongodb-topology-manager #54

imlucas opened this issue Mar 3, 2016 · 2 comments
Assignees

Comments

@imlucas
Copy link
Contributor

imlucas commented Mar 3, 2016

@christkv rewrote all of this in a new beautiful package recently. We should replace our current usage of christkv/mongodb-tools to instead use christkv/mongodb-topology-manager.

@imlucas
Copy link
Contributor Author

imlucas commented Mar 3, 2016

@chistkv

Runner has been most successfully leveraged as global mocha hooks for before/after:
https://github.com/mongodb-js/runner#mocha

Actually using mongodb-tools in a gnarly way currently. lib/index.js
acts as a parent supervisor/child process ctl to simplify config options into more human names/defaults.

lib/worker.js is the childprocess lib/index.js manages.
This is where mongodb-tools code is actually called. After starting, the worker also listens for IPC messages from the parent which
are then translated into calls against the various mongodb-tools#Manager apis.

@imlucas
Copy link
Contributor Author

imlucas commented Sep 26, 2018

Don't think this will happen

@imlucas imlucas closed this as completed Sep 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants