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

procoder-watcher

v0.1.1

Published

Exposes REST APIs to retrieve ProCoder's status

Downloads

4

Readme

NPM version Build Status Coverage Status

procoder-watcher

Exposes REST APIs to retrieve EDIUS ProCoder's transcoding job status

APIs

| Method | Path | Description | Request Params | Query Strings | | ------ | ---------------------- | ------------- | ------------- | ------------- | | GET | /api/logs/:num | Returns the last {num} log entries in reverse chronological order | num must be an integer between 1 to 128 | - |

Response JSON Format

The response is an array of objects. Each object has the following format:

| Field | Type | Description | | ------ | ---------------------- | ------------- | | type | string | "TRANSCODINGJOB" | | status | string | Either of "queued"/"started"/"completed"/"failed" | | source | string | The name of the source file | | queuedTime | string | The time when the transcoding gets started | | error | object | If any error occurred, an error object, otherwise null | | progress | number | Percentage to represent the encoding progress | | destination | string | The name of the output file | | endTime | string | The time when the transcoding completed | | fileSize | number | The file size of the output file |

Install

  • Install Node.js
  • Clone source code and install dependencies
$ git clone [email protected]:kuu/procoder-watcher.git
$ cd procoder-watcher
$ npm install

Run

  • Start the server with specifying parameters (see below)
$ PORT={port number} LOG_PATH={full path} npm start
  • Once the server gets started, you can access the APIs
$ curl http://localhost:3000/api/logs/3
[
  {
    "type": "TRANSCODINGJOB",
    "status": "completed",
    "source": "xxx.avi",
    "queuedTime": "2018-04-17T12:14:22.000Z",
    "error": null,
    "progress": 100,
    "destination": "xxx.mp4",
    "endTime": "2018-04-17T12:16:36.395Z",
    "fileSize": 596487805
  }
  ...
]
  • Timezone is UTC
  • Use DEBUG environ variable for detail logs
$ DEBUG=procoder-watcher npm start

Stop

  • You can stop the server by the following command in the same directory you did npm start
$ npm stop

Parameters

The parameters can be specified via environment variables:

| Variable | Description | Default Value| | ------ | ------------- | ------------- | | PORT | Port number to listen for HTTP requests | 3000 | | LOG_PATH | Directory where the ProCoder log files are located | current directory | | INTERVAL | How frequently the log files are read (in milliseconds) | 1000 | | DEBUG | To enable the debug trace, add procoder-watcher to the DEBUG variable | - (no debug trace) |