npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@rafalolszewski94/scheduler

v1.6.1

Published

Easily manage scheduled tasks in AdonisJS

Downloads

5

Readme

npm-image license-image typescript-image

Pre-requisites

The @rafalolszewski94/scheduler package requires @adonisjs/core >= 5.9.0

Setup

Install the package from the npm registry as follows.

npm i @rafalolszewski94/scheduler
# or
yarn add @rafalolszewski94/scheduler

Next, configure the package by running the following ace command.

node ace configure @rafalolszewski94/scheduler

Defining Scheduled Tasks

You may define all of your scheduled tasks in the start/tasks.ts preloaded file. To get started, let's take a look at an example. In this example, we will schedule a closure to be called every day at midnight. Within the closure we will execute a database query to clear a table:

import Scheduler from '@ioc:rafalolszewski94/Scheduler'
import Database from '@ioc:Adonis/Lucid/Database'

Scheduler.call(async () => {
  Database.from('recent_users').delete()
}).daily()

Scheduling Ace Commands

In addition to scheduling closures, you may also schedule Ace commands and system commands. For example, you may use the command method to schedule an Ace command using the commands name.

import Scheduler from '@ioc:rafalolszewski94/Scheduler'

Scheduler.command('queue:flush').everyFiveMinutes()

Scheduling Shell Commands

The exec method may be used to issue a command to the operating system:

import Scheduler from '@ioc:rafalolszewski94/Scheduler'

Scheduler.exec('node script.js').daily()

Schedule Frequency Options

We've already seen a few examples of how you may configure a task to run at specified intervals. However, there are many more task schedule frequencies that you may assign to a task:

| Method | Description | | ------------------------------- | ------------------------------------------------------- | | .cron('* * * * *') | Run the task on a custom cron schedule | | .everySecond() | Run the task every second | | .everyTwoSeconds() | Run the task every two seconds | | .everyFiveSeconds() | Run the task every five seconds | | .everyTenSeconds() | Run the task every ten seconds | | .everyFifteenSeconds() | Run the task every fifteen seconds | | .everyTwentySeconds() | Run the task every twenty seconds | | .everyThirtySeconds() | Run the task every thirty seconds | | .everyMinute() | Run the task every minute | | .everyTwoMinutes() | Run the task every two minutes | | .everyThreeMinutes() | Run the task every three minutes | | .everyFourMinutes() | Run the task every four minutes | | .everyFiveMinutes() | Run the task every five minutes | | .everyTenMinutes() | Run the task every ten minutes | | .everyFifteenMinutes() | Run the task every fifteen minutes | | .everyThirtyMinutes() | Run the task every thirty minutes | | .hourly() | Run the task every hour | | .hourlyAt(17) | Run the task every hour at 17 minutes past the hour | | .everyOddHour(minutes) | Run the task every odd hour | | .everyTwoHours(minutes) | Run the task every two hours | | .everyThreeHours(minutes) | Run the task every three hours | | .everyFourHours(minutes) | Run the task every four hours | | .everySixHours(minutes) | Run the task every six hours | | .daily() | Run the task every day at midnight | | .dailyAt('13:00') | Run the task every day at 13:00 | | .twiceDaily(1, 13) | Run the task daily at 1:00 & 13:00 | | .twiceDailyAt(1, 13, 15) | Run the task daily at 1:15 & 13:15 | | .weekly() | Run the task every Sunday at 00:00 | | .weeklyOn(1, '8:00') | Run the task every week on Monday at 8:00 | | .monthly() | Run the task on the first day of every month at 00:00 | | .monthlyOn(4, '15:00') | Run the task every month on the 4th at 15:00 | | .twiceMonthly(1, 16, '13:00') | Run the task monthly on the 1st and 16th at 13:00 | | .lastDayOfMonth('15:00') | Run the task on the last day of the month at 15:00 | | .quarterly() | Run the task on the first day of every quarter at 00:00 | | .quarterlyOn(4, '14:00') | Run the task every quarter on the 4th at 14:00 | | .yearly() | Run the task on the first day of every year at 00:00 | | .yearlyOn(6, 1, '17:00') | Run the task every year on June 1st at 17:00 |

These methods may be combined with additional constraints to create even more finely tuned schedules that only run on certain days of the week. For example, you may schedule a command to run weekly on Monday:

import Scheduler from '@ioc:rafalolszewski94/Scheduler'

// Run once per week on Monday at 1 PM...
Scheduler.call(() => {
    // ...
}).weekly().mondays().at('13:00')
 
// Run hourly from 8 AM to 5 PM on weekdays...
Scheduler.command('foo')
         .weekdays()
         .hourly()
         .between('8:00', '17:00')

A list of additional schedule constraints may be found below:

| Method | Description | | ----------------------------- | ----------------------------------------------------- | | .weekdays() | Limit the task to weekdays | | .weekends() | Limit the task to weekends | | .sundays() | Limit the task to Sunday | | .mondays() | Limit the task to Monday | | .tuesdays() | Limit the task to Tuesday | | .wednesdays() | Limit the task to Wednesday | | .thursdays() | Limit the task to Thursday | | .fridays() | Limit the task to Friday | | .saturdays() | Limit the task to Saturday | | .days(days) | Limit the task to specific days | | .between(start, end) | Limit the task to run between start and end times | | .unlessBetween(start, end) | Limit the task to not run between start and end times | | .when(Closure) | Limit the task based on a truth test | | .environments(environments) | Limit the task to specific environments |

Day Constraints

The days method may be used to limit the execution of a task to specific days of the week. For example, you may schedule a command to run hourly on Sundays and Wednesdays:

import Scheduler from '@ioc:rafalolszewski94/Scheduler'

Scheduler.command('emails:send')
         .hourly()
         .days([0, 3])

Between Time Constraints

The between method may be used to limit the execution of a task based on the time of day:

import Scheduler from '@ioc:rafalolszewski94/Scheduler'

Scheduler.command('emails:send')
         .hourly()
         .between('7:00', '22:00')

Similarly, the unlessBetween method can be used to exclude the execution of a task for a period of time:

import Scheduler from '@ioc:rafalolszewski94/Scheduler'

Scheduler.command('emails:send')
         .hourly()
         .unlessBetween('23:00', '4:00')

Truth Test Constraints

The when method may be used to limit the execution of a task based on the result of a given truth test. In other words, if the given closure returns true, the task will execute as long as no other constraining conditions prevent the task from running:

import Scheduler from '@ioc:rafalolszewski94/Scheduler'

Scheduler.command('emails:send')
         .daily()
         .when(() => true);

The skip method may be seen as the inverse of when. If the skip method returns true, the scheduled task will not be executed:

import Scheduler from '@ioc:rafalolszewski94/Scheduler'

Scheduler.command('emails:send')
         .daily()
         .skip(() => true);

When using chained when methods, the scheduled command will only execute if all when conditions return true.

Environment Constraints

The environments method may be used to execute tasks only on the given environments (as defined by the NODE_ENV environment variable):

import Scheduler from '@ioc:rafalolszewski94/Scheduler'

Scheduler.command('emails:send')
         .daily()
         .environments(['staging', 'production']);

Running the Scheduler

Run the scheduler:work ace command, it doesn't need to be put into a cron job, as the scheduler will process the jobs as the time passes