balupton

Use DocPad, GitHub and Prose as a Wiki

This guide will walk you through how you can use a GitHub repository to house your wiki content, have DocPad render it, and automatically update on changes. It's also really nice as we get to benefit from the github project workflow for our wiki, that is issues, pull requests, etc.

We use this workflow heavily by linking the DocPad Website and the DocPad Documentation repositories allowing us to have users edit and submit pull requests for improvements to our documentation, and once merged, the website regenerates automatically.

1. Create a new repository for your Wiki Content

Hypercubed

DocPad: rsync Deploy Script

• Place deploy.sh in {docpad folder}/bin/
• Create (or edit) a .env file in your docpad folder with the following values:

#!/bin/bash
DEPLOY_SOURCE_DIR="out/"
DEPLOY_DEST_DIR="~/public_html/"
DEPLOY_SERVER=deploy-server-name

asafge

/**
 * A generic confirmation for risky actions.
 * Usage: Add attributes: ng-really-message="Are you sure"? ng-really-click="takeAction()" function
 */
angular.module('app').directive('ngReallyClick', [function() {
    return {
        restrict: 'A',
        link: function(scope, element, attrs) {
            element.bind('click', function() {
                var message = attrs.ngReallyMessage;

debasishg

General Background and Overview

1. Probabilistic Data Structures for Web Analytics and Data Mining : A great overview of the space of probabilistic data structures and how they are used in approximation algorithm implementation.
2. Models and Issues in Data Stream Systems
3. Philippe Flajolet’s contribution to streaming algorithms : A presentation by Jérémie Lumbroso that visits some of the hostorical perspectives and how it all began with Flajolet
4. Approximate Frequency Counts over Data Streams by Gurmeet Singh Manku & Rajeev Motwani : One of the early papers on the subject.
5. [Methods for Finding Frequent Items in Data Streams](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.187.9800&rep=rep1&t

tsenart

package main

import (
	"net/http"
	"database/sql"
	"fmt"
	"log"
	"os"
)

sogko

'use strict';

// simple express server
var express = require('express');
var app = express();
var router = express.Router();

app.use(express.static('public'));
app.get('/', function(req, res) {
    res.sendfile('./public/index.html');

kyrcha

var request = require('request'),
	cheerio = require('cheerio'),
	async = require('async');

var base = 'https://www.npmjs.org',
	concurrency = 2;

var q = async.queue(function(task, next) {
	setTimeout(function() {
		console.log('GET ' + task.url);

learncodeacademy

##Setup your server (this would ideally be done with automated provisioning)

• add a deploy user with password-less ssh see this gist
• install forever npm install -g forever

##Install flightplan

• npm install -g flightplan
• in your project folder npm install flightplan --save-dev
• create a flightplan.js file

learncodeacademy

Deploying a node app with Forever is great...until your server restarts unexpectedly. Then your app stops running and you have to re-deploy.

To get around this, we're going to run our node app as an Upstart service. Upstart services are great, because, once started, the system auto-restarts them if they fail, or if the server restarts.

###Step 1: Create a service for your node app

• ssh in as root ssh root@youripaddress
• Create a node-app.conf file in /etc/init
  IMPORTANT: whatever filename you pick is what you will use to start|stop|restart your service i.e. service node-app start

stanislavb

#!/bin/bash

usage() {
    echo "Usage $0 -c mongo_docker_container_name"
}

while [[ $# > 1 ]]
do
key="$1"