typegoose / typegoose/mongodb-memory-server
Consider supporting mongod option `--logpath`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.8k
- Forks
- 191
- Avg merge
- 4h 25m
- Merged PRs (30d)
- 10
Description
Consider supporting mongod option --logpath by either:
- blindly assuming things
- watch the file (if possible)
- dont support
--logpathand just add a option to dump the stdout to a file
watching a file would entail to either have another dependency or a custom made tail (because nodejs does not directly provide a tail -f like functionality)
this should make it easier to collect logs separate from MMS (and maybe anything else the option activates) for mongodb bug reports, like https://jira.mongodb.org/browse/SERVER-81018
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by locating how mongod is spawned and how its stdout and stderr are handled; compare the proposed --logpath, file-watching, and stdout-dump approaches. Done means selecting and implementing a clear way to retain mongod logs separately from MMS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, typescript
- Domain
- databases, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100