35 lines
892 B
Markdown
35 lines
892 B
Markdown
# Scheduler System
|
|
|
|
## Current State
|
|
|
|
The scheduler is implemented through the `cron` Panel module and agent-side `Schedule::Cron` execution.
|
|
|
|
Important references:
|
|
|
|
- `docs/modules/SCHEDULER.md`
|
|
- `Panel/modules/cron/cron.php`
|
|
- `Panel/modules/cron/shared_cron_functions.php`
|
|
- `Agent_Linux/ogp_agent.pl`
|
|
- `Agent-Windows/ogp_agent.pl`
|
|
|
|
## Current Strengths
|
|
|
|
- It can schedule server actions.
|
|
- It can schedule Steam updates and server content actions.
|
|
- It already has a visible UI and agent execution path.
|
|
|
|
## Current Weaknesses
|
|
|
|
- It is too command-string oriented.
|
|
- Customer-safe and admin-only actions are not separated cleanly enough.
|
|
- Task run history is not rich enough.
|
|
- Error reporting and conflict handling need work.
|
|
|
|
## Recommended Direction
|
|
|
|
- typed actions
|
|
- explicit permissions
|
|
- stored task history
|
|
- clear logs and results
|
|
- no customer raw shell commands by default
|
|
|