switch from logging to file to database
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
What do you guys think of switching from writing to a file to instead writing to a database?
Honestly this will take a ton of work, and will really only be beneficial for server running multiple clients.
### Pros
- Easy queries for multiple clients
- Custom settings per client
- Client validation
### Cons
- Overkill for single client systems
- A ton of setup
- Possible vulnerabilities introduced (databases are riddled with incorrect configs)
thoughts?
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. First locate the existing file-logging implementation and clarify the database choice, client model, migration needs, and security expectations with maintainers. Done would require an agreed design and implementation scope, not just a preference between storage approaches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100