meteor-synced-cron - GitLite

KO | EN

gitlite — search

#rust #data-science #security #claude-code #video #kubernetes #database #large-language-models #api #terminal

meteor-synced-cron

(★ 494)

A simple cron system for Meteor. It supports syncronizing jobs between multiple processes.

파일 탐색기

ZIP 다운로드

- - .gitignore
  - npm-shrinkwrap.json
  - README
- - .finished-upgraders
  - .gitignore
  - .id
  - packages
  - platforms
  - release
  - versions
- example.css
- example.html
- example.js
.gitignore
.versions
LICENSE
package.js
README.md
synced-cron-server.js
synced-cron-tests.js
versions.json

# CDN으로 사용하기

jsDelivr

jsDelivr는 공개 GitHub 리포지토리를 별도 설정 없이 CDN으로 즉시 서빙합니다. 버전과 파일을 고르면 웹페이지에 바로 붙일 수 있는 링크와 예시 코드가 만들어집니다.

버전

파일

링크

예시

명령어 용어집

이 문서에서 사용된 명령어를 모아봤습니다. 낯선 명령어가 있다면 펼쳐서 확인해보세요.

🔍

`logger`

설명 보기 ▼

syslog에 메시지 기록.
더 많은 정보: <https://manned.org/logger.1p>.

logger {{message}}

syslog에 메시지 기록:

logger {{message}}

Log a message to syslog:

echo {{log_entry}} | logger

Take input from `stdin` and log to syslog:

🔍

`mongo`

설명 보기 ▼

레거시 MongoDB 셸. 새로운 셸에 대해서는 `mongosh`를 참조.
참고: 모든 연결 옵션은 하나의 문자열로 대체할 수 있습니다: `mongodb://user@host:port/db_name?authSource=authdb_name`.
더 많은 정보: <https://www.mongodb.com/docs/mongodb-shell/>.

mongo

기본 포트(`mongodb://localhost:27017`)에서 로컬 데이터베이스에 연결:

mongo --host {{host}} --port {{port}} {{db_name}}

데이터베이스에 연결:

mongo --host {{host}} --port {{port}} --username {{username}} --authenticationDatabase {{authdb_name}} {{db_name}}

지정된 데이터베이스에서 지정된 사용자 명으로 인증(비밀번호 입력이 필요합니다):

🔍

`tag`

설명 보기 ▼

Edit tags on Mac OS X files (10.9 Mavericks and above).

tag {{[-a|--add]}} {{tag_name1,tag_name2,...}} {{path/to/file}}

Add tags to a file:

tag {{[-r|--remove]}} {{tag_name}} {{path/to/file}}

Remove a tag:

tag {{[-r|--remove]}} \* {{path/to/file}}

Remove all tags from a file:

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

A simple cron system for [Meteor](http://meteor.com). It supports syncronizing jobs between multiple processes. In other words, if you add a job that runs every hour and your deployment consists of multiple app servers, only one of the app servers will execute the job each time (whichever tries first).

## Migrated from percolate:synced-cron littledata:synced-cron

Since the original creator of the project could no longer maintain it, we had to migrate the package to another organisation to allow further maintenance and updates.

To migrate you can simply run

``` sh
$ meteor remove percolate:synced-cron && meteor add littledata:synced-cron
```

## Installation

``` sh
$ meteor add littledata:synced-cron
```

## API

### Basics

To write a cron job, give it a unique name, a schedule and a function to run like below. SyncedCron uses the fantastic [later.js](http://bunkat.github.io/later/) library behind the scenes. A Later.js `parse` object is passed into the schedule call that gives you a huge amount of flexibility for scheduling your jobs, see the [documentation](http://bunkat.github.io/later/parsers.html#overview).

``` js
SyncedCron.add({
  name: 'Crunch some important numbers for the marketing department',
  schedule: function(parser) {
    // parser is a later.parse object
    return parser.text('every 2 hours');
  },
  job: function() {
    var numbersCrunched = CrushSomeNumbers();
    return numbersCrunched;
  }
});
```

To start processing your jobs, somewhere in your project add:

``` js
SyncedCron.start();
```

### Advanced

SyncedCron uses a collection called `cronHistory` to syncronize between processes. This also serves as a useful log of when jobs ran along with their output or error. A sample item looks like:

``` js
{ _id: 'wdYLPBZp5zzbwdfYj',
  intendedAt: Sun Apr 13 2014 17:34:00 GMT-0700 (MST),
  finishedAt: Sun Apr 13 2014 17:34:01 GMT-0700 (MST),
  name: 'Crunch some important numbers for the marketing department',
  startedAt: Sun Apr 13 2014 17:34:00 GMT-0700 (MST),
  result: '1982 numbers crunched'
}
```

Call `SyncedCron.nextScheduledAtDate(jobName)` to find the date that the job
referenced by `jobName` will run next.

Call `SyncedCron.remove(jobName)` to remove and stop running the job referenced by jobName.

Call `SyncedCron.stop()` to remove and stop all jobs.

Call `SyncedCron.pause()` to stop all jobs without removing them.  The existing jobs can be rescheduled (i.e. restarted) with `SyncedCron.start()`.

To schedule a once off (i.e not recurring) event, create a job with a schedule like this `parser.recur().on(date).fullDate();`

### Configuration

You can configure SyncedCron with the `config` method. Defaults are:

``` js
  SyncedCron.config({
    // Log job run details to console
    log: true,

// Use a custom logger function (defaults to Meteor's logging package)
    logger: null,

// Name of collection to use for synchronisation and logging
    collectionName: 'cronHistory',

// Default to using localTime
    utc: false,

/*
      TTL in seconds for history records in collection to expire
      NOTE: Unset to remove expiry but ensure you remove the index from
      mongo by hand

ALSO: SyncedCron can't use the `_ensureIndex` command to modify
      the TTL index. The best way to modify the default value of
      `collectionTTL` is to remove the index by hand (in the mongo shell
      run `db.cronHistory.dropIndex({startedAt: 1})`) and re-run your
      project. SyncedCron will recreate the index with the updated TTL.
    */
    collectionTTL: 172800
  });
```

### Logging

SyncedCron uses Meteor's `logging` package by default. If you want to use your own logger (for sending to other consumers or similar) you can do so by configuring the `logger` option.

SyncedCron expects a function as `logger`, and will pass arguments to it for you to take action on.

```js
var MyLogger = function(opts) {
  console.log('Level', opts.level);
  console.log('Message', opts.message);
  console.log('Tag', opts.tag);
}

SyncedCron.config({
  logger: MyLogger
});

SyncedCron.add({ name: 'Test Job', ... });
SyncedCron.start();
```

The `opts` object passed to `MyLogger` above includes `level`, `message`, and `tag`.

- `level` will be one of `info`, `warn`, `error`, `debug`.
- `message` is something like `Scheduled "Test Job" next run @Fri Mar 13 2015 10:15:00 GMT+0100 (CET)`.
- `tag` will always be `"SyncedCron"` (handy for filtering).

## Caveats

Beware, SyncedCron probably won't work as expected on certain shared hosting providers that shutdown app instances when they aren't receiving requests (like Heroku's free dyno tier or Meteor free galaxy).

## Contributing

Write some code. Write some tests. To run the tests, do:

``` sh
$ meteor test-packages ./
```

## License

MIT. (c) Percolate Studio, originally designed and built by Zoltan Olah (@zol), now community maintained.

Synced Cron was developed as part of the [Verso](http://versoapp.com) project.