ozeias

## railsbox.org:~ ozeias$ vim /usr/local/nginx/conf/vhosts/example.com.conf
# This is for a WordPress installed at /var/www/example.com/blog, and accessed at http://example.com
server {
  listen 80;
  server_name example.com;

  root 	 /var/www/example.com/blog;
  index  index.php;

  access_log /usr/local/nginx/logs/example.com.access.log;

ozeias

## railsbox.org:~ ozeias$ vim /usr/local/nginx/conf/vhosts/blog.example.com.conf
# This is for a WordPress installed at /var/www/example.com/blog, and accessed at http://blog.example.com
server {
  listen 80;
  server_name blog.example.com;

  root 	 /var/www/example.com/blog;
  index  index.php;

  access_log /usr/local/nginx/logs/blog.example.com.access.log;

ozeias

## railsbox.org:~ ozeias$ vim /usr/local/nginx/conf/vhosts/example.com.conf
# This is for a WordPress installed at /var/www/example.com/blog, and accessed at http://example.com/blog
server {
  listen 80;
  server_name example.com;

  root 	 /var/www/example.com;
  index  index.php;

  access_log /usr/local/nginx/logs/example.com.access.log;

ozeias

# Variation on Hashrocket's script for managing the git process
# as documented here: http://reinh.com/blog/2008/08/27/hack-and-and-ship.html
# Create shell scripts out of each of these, put them in your path (~/bin for example)
# chmod 755 them and use like this:
#
# This version of hack is totally different than Hackrockets. I feel that hack implies 
# that you are getting started, not finishing up. sink is Hashrockets hack.
#
# $ hack branch_name
# Test and Implement until done

ozeias

# extracted from marty andrew's presentation on ruby static code analysis
# http://www.slideshare.net/martin_j_andrews/code-quality-analysis

require 'flog'
require 'flay'
require 'roodi'
require 'roodi_task'
require 'metric_fu'

desc "Analyze for code complexity"

ozeias

# 1) Point *.example.com in your DNS setup to your server.
#
# 2) Setup an Apache vhost to catch the star pointer:
#
# <VirtualHost *:80>
#   ServerName example.com
#   ServerAlias *.example.com
# </VirtualHost>
#
# 3) Set the current account from the subdomain

ozeias

/*!
 * jQuery ie6ize: Emulate IE-6 rendering - 11/13/2009
 * http://mankzblog.wordpress.com/2009/11/13/ie6-frame-to-battle-chrome-frame/
 * 
 * Created by Mats Bryntse
 * 
 * Plugin-ified by "Cowboy" Ben Alman
 * http://benalman.com/
 * 
 * Bookmarklet version:

ozeias

def method
  #code
rescue => e
  notify_hoptoad(e)
  render :action => "action"
end

ozeias

Feature: exit statuses
 
  In order to specify expected exit statuses
  As a developer using Cucumber
  I want to use the "the exit status should be" step
 
  Scenario: exit status of 0
    When I run "ruby -h"
    Then the exit status should be 0
    

ozeias

# you'd obviously have more settings somewhere
set :repository, "git@github.com:defunkt/github.git"
set :branch,     "origin/master"

namespace :deploy do
  desc "Deploy the MFer"
  task :default do
    update
    restart
    cleanup