Sign inSign up

fredfeng033/cronflower-ui

By fredfeng033

•Updated 11 days ago

cronflower frontend application

Image
0

88

fredfeng033/cronflower-ui repository overview

⁠cronflower console (web UI)

The web console for cronflower, a distributed, stateful cron scheduler with an optional DAG workflow engine. It is a zero-dependency Node static server plus reverse proxy, so no nginx is needed. Hand it one or more scheduler nodes and it discovers the whole cluster and load-balances the API across it with failover.

⁠What it shows

  • Dashboard, Tasks (list, detail, create or edit), System (Executors, Cluster, Health, Settings), and, when the backend has cronflow, DAG (Workflows and Runs) with a drag or JSON canvas and a live run monitor.
  • Self-balancing. Given one seed it finds every node from /actuator/health and round-robins the API with failover.

⁠Tags

TagMeaning
latestthe newest release
x.y.za specific release, for example 1.0.0
x.ythe latest patch of a minor line

⁠Run

Use the three-node compose template, which wires the console to the cluster for you:

https://github.com/paganini2008/cronflower/blob/main/backend/cronflower-docker/docker-compose.yaml⁠

docker compose up -d
# open http://localhost:7200   (sign in admin / admin123)

⁠Configuration

The container listens on port 80. Map it to a host port, for example 7200:80.

Env varPurpose
SCHEDULER_URLcomma separated scheduler addresses to seed discovery, for example http://cronflower-api-1:8080,http://cronflower-api-2:8080
API_PREFIXREST prefix, must match the backend. Default /cronsmith
CRONFLOW_PREFIXDAG REST prefix, must match the backend. Default /cronflow
DISCOVERYset off to pin to the seeds only. Default on
PORT / WEB_ROOTlisten port (80) and the built SPA directory

Default login is admin / admin123. Full reference: https://github.com/paganini2008/cronflower/blob/main/docs/configuration.md⁠

Tag summary

Content type

Image

Digest

sha256:6528688bc…

Size

47 MB

Last updated

11 days ago

docker pull fredfeng033/cronflower-ui