oakestra / oakestra/documentation
Add new Debugging Guide for DBs
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 0
- Forks
- 3
- Avg merge
- 2h 4m
- Merged PRs (30d)
- 2
Description
To avoid having subpar development/debugging of our DBs it would be very beneficial to collect different ways how to debug the Oakestra DBs. Just using the VSCode MongoDB extension seems to be good but one has to know how to properly configure and set this up (e.g. correct connection strings)
Let's brainstorm together on this.
Contributor guide
No contributing guide indexed for this repository
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 files or tests are named, so first identify the Oakestra databases and their existing development setup. Review the VSCode MongoDB extension and the required connection strings, then define the guide's scope; done means a reviewed debugging guide covering the agreed setup and workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, vscode
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100