SomeKittens

var Browser = require('zombie');

var url = 'http://stackoverflow.com/users/login?returnurl=http%3a%2f%2fchat.stackoverflow.com%2frooms%2f17%2fjavascript';
//url = 'http://chat.stackoverflow.com/rooms/17/javascript';
browser = new Browser({maxWait: 500});
//console.log(browser.cookies);
//browser.cookies(url).set('session', '123');
browser.visit(url, function(e) {
	if (e) return console.error(e);
	//console.log(browser);

SomeKittens

var Browser = require('zombie');

var url = 'http://stackoverflow.com/users/login?returnurl=http%3a%2f%2fchat.stackoverflow.com%2frooms%2f17%2fjavascript';

browser = new Browser();

browser.visit(url, function(e) {
	browser.wait(function(window) {
		return window.document.querySelector('#openid_highlight');
	}, function() {

SomeKittens

function() {
  var myVariable = 'test 123';
  console.log(myVaraible);  // Uh oh!  There's a typo here.
  // JSLint tells us `'myVaraible' was used before it was defined`, catching the error before it's run
};

SomeKittens

wget https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-0.90.9.zip
unzip elasticsearch-0.90.9.zip -d /usr/local/elasticsearch
cd /usr/local/elasticsearch/elasticsearch-0.90.9
bin/plugin -install elasticsearch/elasticsearch-cloud-aws/1.16.0
bin/plugin -install mobz/elasticsearch-head
mv * /usr/local/elasticsearch/
cd ..
rm -R elasticsearch-0.90.9
cd config
echo '' >> elasticsearch.yml

SomeKittens

ln -s swiftmailer/lib/swift_required.php swift_required.php

SomeKittens

We need to edit/test all the plugins, found here: https://github.com/SomeKittens/bot-plugins

Plugins are in this form:

(function() {
  // ...plugin
})();

Switch that to this:

SomeKittens

// assuming you're using express
'use strict';

//express stuffs

var passport = require('passport');
var user = require('./user');

// Configs the passports
require('./passportConfig');

SomeKittens

Keybase proof

I hereby claim:

• I am somekittens on github.
• I am rkoutnik (https://keybase.io/rkoutnik) on keybase.
• I have a public key whose fingerprint is 0E84 45F0 6104 96C0 F62A 1055 6943 A18A 7088 C932

To claim this, I am signing this object:

SomeKittens

'use strict';

var pg = require('pg')
  , bluebird = require('bluebird')
  , connString = require('./config').pg;

bluebird.promisifyAll(pg);
bluebird.promisifyAll(pg.Client.prototype);

module.exports = function() {

SomeKittens

Don't start a hosting company

I talk to a lot of people who are just starting their first startup. An oddly large percentage of them want to know what it'll take to start a webhosting company. This isn't surprising, as web hosting companies like GoDaddy are very visible. Almost everyone needs some sort of hosting to get started. The technical challenges don't seem overwhelming to the beginner - chances are, they've played with some sort of server already. Most importantly, hosting services seem to make a lot of money. To the uninitiated, this seems like a great area to enter. In this essay, I hope to explain why you shouldn't start a hosting service, while also explaining more general pitfalls beginners encounter.

#It's never about the money Lots of beginners fall for the 1% fallacy (the idea that all they need to succeed is 1% of the market) when selecting what to build. They see large, entrenched players as a good sign - there's money to be made here. Large companies are particularly keen on no