githubEdit

Schedule

GitHub Workflow Statusarrow-up-right Releasearrow-up-right GitHub go.mod Go versionarrow-up-right Go Report Cardarrow-up-right GitHub licensearrow-up-right

Schedule message event publishing node

Pre-requisite

  • Nats cluster needs to enable JetStream

  • Services and applications should work together the same nats tenant

  • Each node defines a NODE name that is unique, through which Schedule will be assigned to the node

Deploy

The principle of the Schedule service is to publish the job message sync up to the worker node cluster. Multi-node can improve the number of tasks and disaster recovery.

The main container image is:

  • ghcr.io/weplanx/schedule:latest

  • registry.cn-shenzhen.aliyuncs.com/weplanx/schedule:latest

The case will use Kubernetes deployment orchestration, replicate deployment (modify as needed).

Environement

MODE

  • Working mode, default debug

NODE *required

  • Node name

NATS_HOSTS *required

  • Nats connection host, use , split

NATS_NKEY *required

  • Nats NKEY authentication

Client

The client end for managing Schedule configuration, installed in the application:

Initialize

Set

Status

List Keys

Get Info

Start or Stop

Remove

License

BSD-3-Clause Licensearrow-up-right

Last updated