karmi

# Rake task to launch multiple Resque workers in development/production with simple management included

require 'resque/tasks'    # Require Resque tasks

namespace :workers do

  # = $ rake workers:start
  #
  # Launch multiple Resque workers with the Rails environment loaded,
  # so they have access to your models, etc.

nesquena

## DNS

@dns = Fog::DNS.new(:provider => 'Linode', :linode_api_key => LINODE_KEY)
if @zone = @dns.zones.all.find { |z| z.domain == ZONE }
  puts "Found zone #{@zone.inspect}"
else
  @zone = @dns.zones.create(:domain => ZONE, :email  => ZONE_EMAIL)
  puts "Creating zone #{@zone.inspect}"
end

sbusso

#!/usr/bin/env ruby
# == Simple Daemon
#
# A simple ruby daemon that you copy and change as needed.
# 
# === How does it work?
#
# All this program does is fork the current process (creates a copy of
# itself) then exits, the fork (child process) then goes on to run your
# daemon code. In this example we are just running a while loop with a

mklnz

# I got tired of uploading to /tmp then moving to the correct location, so these two convenience methods will save you a lot of time in the long run.

# Helper method to upload to /tmp then use sudo to move to correct location.
def put_sudo(data, to)
  filename = File.basename(to)
  to_directory = File.dirname(to)
  put data, "/tmp/#{filename}"
  run "#{sudo} mv /tmp/#{filename} #{to_directory}"
end

wilmoore

UMD-Inspired JS Module Boilerplate

This is the module format you don't know you need until you need it. Write your module once and have it work in a CJS/NodeJs, AMD, YUI (v3+), or Browser Global environment.

Best Used When...

• You are migrating from namespaced (err, globals) code to either AMD or CJS modules or both.
• You can't yet factor out browser globals but also need to test your code via NodeJS (e.g. Mocha).

Benefits & Trade-offs

domenic

This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.

You're Missing the Point of Promises

Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:

getTweetsFor("domenic", function (err, results) {
 // the rest of your code goes here.

ccashwell

#!/bin/bash
# This is an example of OAUTH2 authorization via GitHub and adding a new (optionally generated) SSH key to your account. 
# If generated, the key is put in the default location with no password. Security is obviously relaxed for brevity's sake. Enjoy. 

read -p "GitHub Username: " uname
read -s -p "GitHub Password: " passwd
if [[ "$uname" == "" || "$passwd" == "" ]]; then
  echo -e "\n\nCan't set up your GitHub SSH keys without authorization. You're on your own now, champ."
  exit 1
fi

iamdustan

(function ($) {


  function autoSubmitHandler ($input, $button) {
    var self = this;
    this.$input = this;
    this.$button = $button;

    this.$input.on('keydown', function (e) { self.handleInputKeydown(e); });
    this.$input.on('blur', function (e) { self.handleInputBlur(e); });