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

@cloud-cli/crond

v1.5.2

Published

A crontab-like runner using [NPM cron package](https://npmjs.com/cron).

Downloads

51

Readme

crond

A crontab-like runner using NPM cron package.

Oh, but why can't you just use crontab? What's this?

Well, I could. But maybe I want to run cronjobs on my phone or inside a container and I don't want to fiddle with the host file system. This is completely userland.

Install

npm i -g @cloud-cli/crond

Make sure the global NPM folder is part of $PATH.

Usage

  • run crond to schedule jobs defined in the configuration file
  • run crond -d or crond --daemon to detach from your shell (run in the background, like a daemon)
  • the daemon writes a log to $CRON_LOGS_FOLDER/crond.log

Environment variables

| name | description | |-|-| | CRON_LOGS_FOLDER | Path to a folder where logs will be placed per job. Default is /tmp/cronjobs | | CRON_JOBS_FILE | Name of the JSON file where jobs are defined. Default is jobs.json | | DEBUG | Set it to get debug logs from crond |

Jobs file format

  • Create jobs.json or jobs.yaml at either $HOME or the current folder.
  • Each job can have one or more commands to execute.
  • The current folder can be specified
  • Interval follows the same syntax as crontab. Use https://crontab.guru/ to verify
  • Give it a short name. This name is used to create the output log file.
jobs:
  - name: job-name
    interval: '0/5 * * *'
    cwd: /tmp/abc
    commands:
      - echo "Hello mom!"
      - cat file.txt
      - wget https://example.com

  - name: another-job-name
    interval: '0 0 * * *'
    cwd: /tmp/abc
    command: npm update

services:
  - name: http-server
    restart: true
    restartInterval: 5000
    cwd: /var/www
    command: node /opt/http.js

API

interface Job {
  name: string;
  interval: 'once' | string;
  cwd: string;
  command?: string;
  commands?: string[];
}

interface Service {
  name: string;
  command: string;
  restart?: boolean;
  restartInterval?: number;
  cwd?: string;
}