The web walker motss

Committing Code

General Rules

Make atomic commits of changes, even across multiple files, in logical units. That is, as much as possible, each commit should be focused on one specific purpose.
As much as possible, make sure a commit does not contain unnecessary whitespace changes. This can be checked as follows:

$ git diff --check

In addition to awesome docs #228, Bower deserves a proper logo. See below for sketches. I'm curious if you think any of these are worth me putting more effort into.

Take a look at Yeoman right now.

The other two entities have awesome logos. Bower's got to represent.

Update May 2017

Eric Bidelman has documented some of the common workflows possible with headless Chrome over in https://developers.google.com/web/updates/2017/04/headless-chrome.

Update

If you're looking at this in 2016 and beyond, I strongly recommend investigating real headless Chrome: https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md

Windows and Mac users might find using Justin Ribeiro's Docker setup useful here while full support for these platforms is being worked out.

	// Create our server
	var server;
	server = http.createServer(function(req,res){
	// Set CORS headers
	res.setHeader('Access-Control-Allow-Origin', '*');
	res.setHeader('Access-Control-Request-Method', '*');
	res.setHeader('Access-Control-Allow-Methods', 'OPTIONS, GET');
	res.setHeader('Access-Control-Allow-Headers', '*');
	if ( req.method === 'OPTIONS' ) {
	res.writeHead(200);

	/**
	* Convert From/To Binary/Decimal/Hexadecimal in JavaScript
	* https://gist.github.com/faisalman
	*
	* Copyright 2012-2015, Faisalman <[email protected]>
	* Licensed under The MIT License
	* http://www.opensource.org/licenses/mit-license
	*/

	(function(){

	var express = require('express'),
	routes = require('./routes'),
	upload = require('./routes/upload'),
	http = require('http'),
	https = require('https'),
	fs = require('fs'),
	path = require('path'),
	httpApp = express(),
	app = express(),
	certPath = "cert";

	// NOTE: I previously suggested doing this through Grunt, but had plenty of problems with
	// my set up. Grunt did some weird things with scope, and I ended up using nodemon. This
	// setup is now using Gulp. It works exactly how I expect it to and is WAY more concise.
	var gulp = require('gulp'),
	spawn = require('child_process').spawn,
	node;

	/**
	* $ gulp server
	* description: launch the server. If there's a server already running, kill it.

	Secure sessions are easy, but not very well documented.
	Here's a recipe for secure sessions in Node.js when NginX is used as an SSL proxy:

	The desired configuration for using NginX as an SSL proxy is to offload SSL processing
	and to put a hardened web server in front of your Node.js application, like:

	[NODE.JS APP] <- HTTP -> [NginX] <- HTTPS -> [PUBLIC INTERNET] <-> [CLIENT]

	Edit for express 4.X and >: Express no longer uses Connect as its middleware framework, it implements its own now.

	# Basically the nginx configuration I use at konklone.com.
	# I check it using https://www.ssllabs.com/ssltest/analyze.html?d=konklone.com
	#
	# To provide feedback, please tweet at @konklone or email [email protected].
	# Comments on gists don't notify the author.
	#
	# Thanks to WubTheCaptain (https://wubthecaptain.eu) for his help and ciphersuites.
	# Thanks to Ilya Grigorik (https://www.igvita.com) for constant inspiration.

	server {

	# to generate your dhparam.pem file, run in the terminal
	openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048