Closed rootwarp closed 1 year ago
@xellos00 As you know, we are not storing executing information of the plugin. And I think it could be better to store and track information at the DB.
For the starting point, I'll track the PID of the plugin. Do you have any other ideas to store?
@rootwarp Guess that's best idea, no matter what I think it's a requirement to set up DB. but Let's have a meeting at some point. I will ping you. for more discussions.
Plugin info - config - DB
AS-IS VATZ get <- Config
To-BE Config push -> DB VATZ get <- DB
CLI STOP, KILL
enable/disable
@meetrick Good to see through DB get .
Plugin info - config - DB
- AS-IS VATZ get <- Config
- To-BE Config push -> DB VATZ get <- DB
CLI STOP, KILL enable/disable
@meetrick Good to see through DB get .
Let's put a vote.
Plugin info - config - DB
- AS-IS VATZ get <- Config
- To-BE Config push -> DB VATZ get <- DB
CLI STOP, KILL enable/disable @meetrick Good to see through DB get .
Let's put a vote.
- AS-IS ππ½
- To-BE β€οΈ
Output by vote
To-BE Config push -> DB VATZ get <- DB
@rootwarp As we previously vote, I will take this issue to migration feature config.yaml.
Tasks
Config.yaml
into DB@xellos00
@rootwarp & @xellos00
Checklist
[ ] Others(etc. e.g, documentation,...)
Please describe, what it's about or related Problem with
When a plugin is executed, executing information should be managed in SQLite for maintenance reason.
Describe the output that you are expecting for above
Describe alternatives you've considered
N/A
Additional context