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

graphile-worker-decoupled

v0.1.0-alpha.10

Published

Job queue for PostgreSQL

Downloads

26

Readme

Documentation

Check out the document for the original graphile-worker: https://github.com/graphile/worker/blob/master/README.md

What's this fork for

If your DBA does not allow admin access to the database to install extensions and schema, nor would they pass you the name/pw to be put inside a NodeJS application.

In any case where the database setup needed to be decoupled with the nodejs application setup, you should use this fork.

Guide

Database Setup

Let your DBA setup the schema with their own admin account

cd sql
psql -f 000000.sql -v SCHEMA_NAME=my_worker_schema "postgresql://admin:admin@host:port/mydb"
psql -f 000001.sql -v SCHEMA_NAME=my_worker_schema "postgresql://admin:admin@host:port/mydb"

NodeJs Setup

Lauch your NodeJs application with worker account (NOTE: make sure the account has access to the db mydb in this case)

npx graphile-worker -c "postgresql://worker:worker@host:port/mydb" -s my_worker_schema