Dietpi-Software | Cronicle

[Goldenfreddy0703]

Creating a software request

Formal software information

• Software title | Cronicle
• Short description | Distributed task scheduler and job automation platform with a web-based UI
• Official URL (if available) | https://cronicle.net/
• GitHub URL (if available) | https://github.com/jhuckaby/Cronicle
• (Official) install documentation | https://github.com/jhuckaby/Cronicle/blob/master/docs/Setup.md

Are there similar/alternative software titles available with DietPi-Software?

• cron (built-in)
• systemd timers
• Jenkins (automation server)
• Watchtower (for container updates)

What makes your requested software better than the above solutions, if available?

• Cronicle provides a rich web UI for scheduling and monitoring jobs, unlike plain cron or systemd timers.
• It includes job history, detailed logs, success/failure status, retries, and manual re-runs.
• Designed to run across multiple machines (distributed mode), which is more scalable than basic cron.
• Easier and more approachable than Jenkins for simple to mid-complex automation workflows.

How can DietPi make the installation easier or compatible, than following the install instructions or do APT installation, if available?

• The official Cronicle install instructions require several steps:
  • Installing Node.js (specific supported version)
  • Cloning the GitHub repository
  • Running npm install
  • Creating config directories and setting permissions
• DietPi could automate these tasks and integrate Cronicle as a systemd service, making installation as easy as:

  dietpi-software install cronicle

• DietPi could also manage:
  • Default ports
  • Firewall settings
  • Log rotation
  • Optionally automated backups of Cronicle data

Can you provide the installation steps that you would suggest DietPi-Software to do?

1. Install Node.js (LTS) and required system packages
2. Clone Cronicle repository to /opt/cronicle
3. Run npm install to install dependencies
4. Create directories for data, logs, and plugins
5. Create a dedicated user (e.g., cronicle) and set ownership
6. Create and enable a systemd service for Cronicle
7. Set correct permissions and environment variables
8. Start and test Cronicle service
9. Optionally open port 3012 in firewall

Are you willing to help maintaining the software installation, e.g. in case of needed setup changes due to updates etc.?

• Yes, I am willing to help with maintenance, testing, and future update support if needed.

[dudumaroja]

Cronicle has a sucessor form the same creator xyops

https://github.com/pixlcore/xyops