How jiawesoft/jiascheduler works
Project type and purpose
• Jiascheduler is a distributed, high-performance, dynamically configurable task scheduler written in Rust.
• It exposes four main executables:
1. console (the Web UI + REST API server)
2. comet (WebSocket gateway for agents)
3. agent (local task executor + SSH proxy)
4. jiascheduler (a bundled single-node package of the above three)
File structure
Top-level workspace crates:
• automate/… (core scheduler library: bus, comet server/bridge, scheduler, SSH)
• openapi-derive/… (codegen macros for the REST API)
• openapi/… (console service: API, entity layer, logic, middleware, state; Rust web server exposing OpenAPI)
• migration/… (database migration CLI + SQL scripts)
• crates/leader-election/… (leader-election library for high availability)
• src/bin/agent.rs, comet.rs, console.rs, jiascheduler.rs (entrypoints)
• docker-compose.yml, Dockerfile, .env, assets/, examples/, dist/…
README for additional insights
• Confirms four executables (console, comet, agent, bundled).
• Browser ↔ Console (HTTP + WebSocket for web SSH)
• Console ↔ MySQL + Redis
• Console ↔ Comet (internal RPC or Redis pub/sub)
• Comet ↔ Agent (WebSocket)
• Agent ↔ target hosts (via SSH)