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

erichurst

# MySQL.  Versions 4.1 and 5.0 are recommended.
#
# Install the MySQL driver:
#   gem install mysql2
#
# And be sure to use new-style password hashing:
#   http://dev.mysql.com/doc/refman/5.0/en/old-client.html
development:
  adapter: mysql2
  encoding: utf8

benfoxall

Using default OSX apache httpd to serve ~/Sites/foo at http://foo.local

By configuring dns and using virtual hosts - you can automatically serve folders in your ~/Sites directory under a local domain.

point *.local to localhost

Wildcard DNS is a better option that editing your /etc/hosts file for every site, there are a few ways to do this.

set up a local dns

http://mikeferrier.com/2011/04/04/setting-up-wildcard-dns-on-localhost-domains-on-osx/

schinckel

/*

# jquery.couch.longpoll.js #

A handler that can be used to listen to changes from a CouchDB database,
using long-polling.

This seemed to be a bit simpler than using continuous polling, which I
was unable to get working with jQuery.

elucas

When you submit the form#filters_form, it requests the response in the background, replaces the existing contents of #article_blocks with the #article_blocks from the response, and updates the url with the params given.

Oh, and if it fails, it redirects you to the form url, so that you're not left in a broken ajax state.

So:

• No fancy ajax logic server-side
• No fancy ajax logic client-side
• Just the bit of content you wanted gets updated

Disclaimer: Tweaks would be needed for POST forms

olexpono

/**********************************************/
/*
/*
/* Crate -- Theme for Chrome DevTools
/* Last Update :: September 2013
/*
/* based on:
/* mnml by Michael P. Pfeiffer
/* Based on a Gist by Ben Truyman. Further attr:
/* https://gist.github.com/3040634

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

booleanbetrayal

'use strict';

module.exports = function(grunt) {

    // load all grunt tasks
    require('matchdep').filterDev('grunt-*').forEach(grunt.loadNpmTasks);


    // configurable paths
    var paths = {

olorton

#!/bin/bash

while getopts "v:" OPTION; do
    case $OPTION in
        v) shift; verbose=true;;
        # Unknown option. No need for an error, getopts informs
        # the user itself.
        \?) exit 1;;
    esac
done

joonty

#!/bin/sh
### BEGIN INIT INFO
# Provides:          unicorn
# Required-Start:    $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Manage unicorn server
# Description:       Start, stop, restart unicorn server for a specific application.
### END INIT INFO