Another debug data storage support
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 202
- Forks
- 147
- Avg merge
- 1h 54m
- Merged PRs (30d)
- 1
Description
We want to use this extension in our staging zone, but the problem is that we have multiple application servers behind balancing server. We tried to extend this module, but we needed to extend 3 different classes:
- Module (LogTarget forcing on application start)
- LogTarget (File saving)
- DefaultController (Information fetching from file)
This issue may be fixed with using a storage class with get, set, getManifest and setManifest methods or something like this. We want to use Redis for this task. What do you think?
I can implement this in PR
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
Start by reading the Module, LogTarget, and DefaultController classes named in the issue to trace how debug data is forced, saved, and fetched. Review the proposed get, set, getManifest, and setManifest storage contract, then determine what integration and validation are needed for Redis-backed storage across multiple application servers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, redis
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100