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

acl-sequelize-backend

v0.0.7

Published

A Sequelize.js backend for node_acl

Downloads

4

Readme

ACL Sequelize

Build Status Coverage Status

node_acl implementation for Sequelize Currently working only with Postgres.

Installation

npm install sequelize
npm install pg
npm install acl
npm install acl-sequelize-backend

Setup

var NodeAcl = require('acl');
var Sequelize = require('Sequelize');
var SequelizeBackend = require('acl-sequelize-backend');
var db = new Sequelize('postgres://postgres:[email protected]:5432/myawesomedb');

var aclOptions = {};
var tablePrefix = 'acl_';

var acl = new NodeAcl(new SequelizeBackend(db, tablePrefix, aclOptions));

API

new SequelizeBackend(db, prefix, options)

Arguments

  db        {Function} Sequelize db instance.
  prefix    {String} Prefix for generated tables
  options   {Object} Options provided to the backend

Options can contain these fields:

Note: These are also the defaults if nothing is provided.

var options = {
  meta: 'meta',               // Table name for meta bucket
  parents: 'parents',         // Table name for parents bucket
  permissions: 'permissions', // Table name for permissions bucket
  resources: 'resources',     // Table name for resources bucket
  roles: 'roles',             // Table name for roles bucket
  users: 'users',             // Table name for users bucket
  sync: true,                 // Should tables be automatically created using sequelize sync method
  debug: false                // Enable debug (shows sql on sync if enabled)
};

Migrations

If you want to use migrations to generate tables instead of automatic sync, You can pull them from SequelizeBackend like this:

First, make sure you disable automatic sync when initializing acl:

var acl = new NodeAcl(new SequelizeBackend(db, 'acl_', {
    sync: false
}));

Then generate migration file and add this to it:

// migrations/add_acl.js

var SequelizeBackend = require('acl-sequelize-backend');

module.exports = {
  up: function (queryInterface, Sequelize) {
    var options = { prefix: 'acl_' };
    return SequelizeBackend.migration.up(queryInterface, Sequelize, options);
  },

  down: function (queryInterface, Sequelize) {
    var options = { prefix: 'acl_' };
    return SequelizeBackend.migration.down(queryInterface, Sequelize, options);
  }
};

Both up and down methods accept 3rd parameter options which can contain table names for each bucket

var options = {
  prefix: '',                 // Prefix for table names
  meta: 'meta',               // Table name for meta bucket
  parents: 'parents',         // Table name for parents bucket
  permissions: 'permissions', // Table name for permissions bucket
  resources: 'resources',     // Table name for resources bucket
  roles: 'roles',             // Table name for roles bucket
  users: 'users'              // Table name for users bucket
};

NOTE: Make sure that table names and prefix provided here match with table names and prefix provided to the backend.

It is recommended to just use defaults in order to avoid any issues with naming.

Tests

npm test