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

agenda-admin

v1.1.4

Published

A dashboard for agenda.js

Downloads

12

Readme

Agenda Admin

logo

A Dashboard for Agenda


Features

  • Jobs status, refresh interval is 15 seconds by default
  • Search jobs by name, including autocomplete
  • Filter jobs by metadata and status
  • View job details
  • Delete and requeue jobs
  • Schedule a new job

Prerequisites

Required version of MongoDB: >2.6.0


Middleware usage

Agenda Admin can be used as express middleware, using the mountAgendaAdmin function. As an argument, it takes an object with the following fields:

  • publicUrl - the URL at which the frontend is served
  • mountPath - the path which the middleware should be mounted (passed to app.use())
  • expressApp - the express app
  • agenda - an agenda instance
  • options - an optional argument, the object can have the following properties:
    • itemsPerPage
    • username
    • password

Example:

const express = require('express');
const Agenda = require('agenda');
const { mountAgendaAdmin } = require('agenda-admin');

const app = express();

// Other express middleware

const agenda = new Agenda({ db: { address: 'mongodb://127.0.0.1/agendaDb' } });

mountAgendaAdmin({
  publicUrl: 'http://localhost:7878/agenda-admin',
  mountPath: '/',
  expressApp: app,
  agenda
});

app.listen(7878);

Docker usage

The docker container exposes port 7878

At this point, AgendaAdmin does not support port re-mapping, so the container should be connected to port 7878 only

docker run -p 7878:7878 \
--env CONNECTION_STRING=mongo://username:password@host/database \
--env COLLECTION=collection lexissolutions/agenda-admin:latest

Docker environment configuration

| name | description | required | default value | | ----------------- | ------------------------------------------------------------------- | -------- | ------------- | | CONNECTION_STRING | MongoDB connection string | yes | | | COLLECTION | MongoDB collection of jobs | no | agendaJobs | | ITEMS_PER_PAGE | Number of jobs per page | no | 20 | | AGENDA_USERNAME | Username used for authentication (only when a password is provided) | no | admin | | AGENDA_PASSWORD | If no password is provided, no authentication will be required | no | |


Contributing

Install dependencies

yarn install

Running

Inside the api directory create an .env.development file with CONNECTION_STRING and COLLECTION variables, then run yarn dev.
You can also run yarn start in the api and client directories.

Running tests

Inside the api directory create an .env.testing file with CONNECTION_STRING and COLLECTION variables, then run yarn test.

Commit messages

Agenda Admin uses conventional commits format.