repeatingbeats

/**
 * Example structure for nodeunit tests with nested groups and setup/teardown
 * functions. Run | nodeunit nodeunit_example.js | to see a printout of
 * function names in the order that they are called. There aren't any actual
 * tests here.
 */

process.env.NODE_ENV = 'test';

var testCase = require('nodeunit').testCase;

felixhummel

# bash completion for rake
#
# some code from on Jonathan Palardy's http://technotales.wordpress.com/2009/09/18/rake-completion-cache/
# and http://pastie.org/217324 found http://ragonrails.com/post/38905212/rake-bash-completion-ftw
# 
# For details and discussion
# http://turadg.aleahmad.net/2011/02/bash-completion-for-rake-tasks/
#
# INSTALL
#

fidothe

# If you want to use gem pristine with RVM gemsets after ditching MacPorts for Homebrew 
# in order to recompile native gems you need to exclude things in the global gemset
# probably rake, bundler, maybe rdoc 
gem list --no-versions | grep -v bundler | grep -v rake | xargs -n1 gem pristine

jhsu

ctags tips

Install ctags

brew install ctags-exuberant

Index tags

While in the root of the project

jhsu

git-hub

This script opens a url to the github commit page

Install

add to a folder in $PATH (ie, /usr/local/bin, or if you have ~/bin part of your path). If the current branch is tracking a remote branch that is on github:

git hub # outputs the url to the most recent commit and opens it in default browser (if the commit has been pushed)

git hub -2 # opens the url to the 2nd most recent commit

jhsu

/usr/local/bin/ctags --exclude=.git --exclude=log -R * ~/.rvm/gems/`rvm current`/*

wheresalice

www:
 requirements:
  - faye
  - jade

bricker

Rails: Synchronizing your development database with your production database using Rake tasks

July 30, 2012

If you run an active website with lots of new content every day, it's often helpful to keep your local database up-to-date with your production database, so when you're working on the application locally you're working with fresh content.

Here are a couple rake tasks that you can copy-and-paste into your local Rails application which will make this syncing process a one-step process.

BaseCase

{exec} = require 'child_process'


task 'test', 'Runs all Jasmine specs in spec/ folder', ->
  test()

task 'compile', 'Compiles coffee in src/ to js in bin/', ->
  compile()

task 'stitch', 'Stitches all app .js files', ->

bfleischer

#!/bin/sh -x

# These variables are always passed to build.sh
DIST_DIR="$1"
TMP_DIR="$2"
ROOT_DIR="$3"

PROJNAME="fuse_wait"

DESTDIR="usr/local/bin"