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

couchpenter

v0.3.0

Published

CouchDB database and document setup tool.

Downloads

7

Readme

Build Status Dependencies Status Coverage Status Published Version npm Badge

Couchpenter

Couchpenter is a CouchDB database and document setup tool.

This is handy when you want to create or delete CouchDB databases and documents based on a predefined setup file, either from the command-line or programmatically.

A common usage scenario is to hook up Couchpenter to application start up code, ensuring CouchDB to have the required databases along with any data, design, and replication documents, before the server starts listening.

Another usage is for integration testing, either from test libraries (e.g. Mocha's beforeEach/afterEach), or from a Continuous Integration build pipeline (e.g. resetting the databases prior to running the test suites).

Installation

npm install -g couchpenter 

Usage

Create a sample couchpenter.json setup file:

couchpenter init

Execute a task against a CouchDB URL using default couchpenter.json setup file:

couchpenter <task> -u http://user:pass@host:port

CouchDB URL can also be set via COUCHDB_URL environment variable:

(*nix)

export COUCHDB_URL=http://user:pass@host:port

(Windows)

set COUCHDB_URL=http://user:pass@host:port

Execute a task using custom setup file:

couchpenter <task> -u http://user:pass@host:port -f somecouchpenter.json

Tasks:

Programmatically:

// use default couchpenter.json setup file
var couchpenter = new (require('couchpenter'))(
  'http://user:pass@host:port'
);

// use custom setup file
var couchpenter = new (require('couchpenter'))(
  'http://user:pass@host:port',
  { setupFile: 'somecouchpenter.json' }
);

// use setup object (instead of setup file)
var couchpenter = new (require('couchpenter'))(
  'http://user:pass@host:port',
  { dbSetup: {
      "db1": [
        { "_id": "doc1", "foo": "bar" },
        { "_id": "doc2", "foo": "bar" },
        "path/to/doc3file.json"
      ]
    }
  }
);

// prefix the database names
// handy for running multiple tests in parallel without interrupting each other
var couchpenter = new (require('couchpenter'))(
  'http://user:pass@host:port',
  { prefix: 'testrun123_' }
);

// specify a base directory for the documents specified in setup file
var couchpenter = new (require('couchpenter'))(
  'http://user:pass@host:port',
  { dir: '../some/dir/' }
);

// set up databases and documents
couchpenter.setUp(function (err, results) {
});

// delete databases and documents
couchpenter.tearDown(function (err, results) {
});

// delete databases and documents, then set up databases and documents
couchpenter.reset(function (err, results) {
});

// delete documents, then set up documents
couchpenter.resetDocuments(function (err, results) {
});

// warm up all views specified in design documents
couchpenter.warmViews(function (err, results) {
});

// warm up all views specified in design documents every minute (scheduled)
couchpenter.warmViews('* * * * *', function (err, results) {
});

Check out lib/couchpenter for other available methods.

Configuration

Couchpenter setup file is just a simple JSON file:

{
  "db1": [
    { "_id": "doc1", "foo": "bar" },
    { "_id": "doc2", "foo": "bar" },
    "path/to/doc3file.json"
  ],
  "db2": [
    { "_id": "doc4", "foo": "bar" },
    "path/to/modulename"
  ],
  "db3": [],
  "_replicator": {
    {
      "_id": "db1_pull",
      "source": "http://user:pass@remotehost:5984/db1",
      "target": "db1",
      "user_ctx": {
        "name": "user",
        "roles": ["_admin"]
      },
      "continuous": true
    }
  }
}

Property keys are the names of the databases, property values are the documents in each database.

A document can be represented as:

  • an object
  • a file path string containing a JSON document, file name must end with .json
  • a module path string

Paths are relative to current directory if it's used from command-line, or relative to opts.dir if it's used programmatically (defaults to current directory if opts.dir is not specified).

Colophon

Developer's Guide

Build reports:

Related Projects: