ingoradatz

// Short module explanation             // Something to gather my thoughts
//                                      // I think this looks cool.
                                        //
module.exports = the_exported_function  // Modules are a function. Always.
                                        //
module.exports.extra = extra            // Additional API entry points if
module.exports.other = other            // desired.
                                        //
var util = require('util')              // Other packages from npm or core
var assert = require('assert')          // No comma-first due to lots of

ingoradatz

Why?

This command attaches code (pull request) to an existing issue. This prevents:

• creating a new issue when opening a new pull-request
• splitting an on-growing discussion from an issue into an pull request issue

Usage?

You can use personal and organization github names and their branches.

git pull-request -i issue-number-without-the-# -b request-to-branch -h request-from-branch

fdmanana

1. Introduction to the replicator database

A database where you PUT/POST documents to trigger replications and you DELETE to cancel ongoing replications. These documents have exactly the same content as the JSON objects we used to POST to /_replicate/ (fields "source", "target", "create_target", "continuous", "doc_ids", "filter", "query_params".

Replication documents can have a user defined "_id". Design documents (and _local documents) added to the replicator database are ignored.

The default name of this database is _replicator. The name can be changed in the .ini configuration, section [replicator], parameter db.

2. Basics