A task scheduler and automation tool for defining and running recurring jobs via recipes with schedule, cron, and webhook triggers.
Leprechaun is a task scheduling and automation tool that allows users to define recurring jobs as recipes, which can be triggered on a schedule, via cron patterns, or through webhooks. It provides a flexible way to automate workflows with support for step execution, piping, failure handling, and remote command execution.
System administrators and developers who need to automate repetitive tasks, such as scheduled backups, log rotations, or deployment scripts, with support for both local and remote execution.
Developers choose Leprechaun for its simple YAML-based recipe system that combines scheduling, webhooks, and cron patterns with advanced features like step piping, failure handling, and remote execution, offering a unified tool for diverse automation needs.
You had one job, or more then one, which can be done in steps
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports scheduled, cron-pattern, and webhook-triggered recipes, allowing automation based on time or external events without extra scripting, as shown in the YAML examples.
Features step piping with `}>` syntax and optional failure halting using `!`, providing precise workflow execution and error handling, detailed in the README examples.
Enables running specific steps on remote machines via `rmt:host` syntax, facilitating distributed automation without external tools, as demonstrated in the recipe configurations.
Allows use of environment variables in steps via `$variable` syntax, making recipes adaptable to different setups, mentioned in the variable usage section.
Steps execute linearly, and misconfigured async steps can block others, as warned in the README, limiting parallel execution and causing potential bottlenecks.
Remote execution requires installing separate `leprechaunrmt` services on each host, adding deployment and maintenance overhead, with sparse configuration guidance.
The README has typos and assumes familiarity, and as a niche tool, it lacks the community support, plugins, and integrations of established alternatives like cron.