mrrooijen

# Guide
# Configure the essential configurations below and do the following:
# 
#   Repository Creation:
#     cap deploy:repository:create
#     git add .
#     git commit -am "initial commit"
#     git push origin master
# 
#   Initial Deployment:

juliamae

Deploying a Rails 3 App with EC2 + S3 + Ubuntu + Capistrano + Passenger
=======================================================================

EC2 Setup
---------
1 Launch New ec2 instance - ami-1634de7f
2 Create elastic IP [ELASTIC_IP] and associate it with instance
3 go to domain registrar DNS settings, @ and www to ELASTIC_IP
4 set the `:host` in `config/deploy.rb` to ELASTIC_IP

raggi

class DiskWriter < EM::Connection
  # A random stab in the dark at somethign that's loosely efficient. Assuming
  # you have a larger page size than 4kb, you'll probably still want ruby to
  # write a ton of pages at a time to anything resembling a spindle. On most
  # systems, this will default to 64kb. It's possible you may get better
  # performance going much higher. If you end up GC bound, or other operations
  # are causing leak like behavior, then you may find higher tunings become
  # less efficient in production over time. It is also worth noting that some
  # versions ::Queue do not free their buffer pages.
  DEFAULT_THRESHOLD = 16384 * `getconf PAGESIZE`.to_i

dhh

# autoload concerns
module YourApp
  class Application < Rails::Application
    config.autoload_paths += %W(
      #{config.root}/app/controllers/concerns
      #{config.root}/app/models/concerns
    )
  end
end

czottmann

worker:     QUEUE=* bundle exec rake environment resque:work 
scheduler:  bundle exec rake environment resque:scheduler

pjkelly

How to setup your VMWare Fusion images to use static IP addresses on Mac OS X

At Crush + Lovely, we use Railsmachine's Moonshine to automate the configuration of our servers. When writing our deployment recipes, VMWare Fusion's ability to take snapshots and rollback to these snapshots is a huge timesaver because it takes just seconds to roll a server image to it's original state.

When you're just configuring a single server, having a static IP address for your server image isn't too important, but when you're configuring multi-server setups, it can be useful to duplicate a number of server images and give each a static IP address so you can consistently deploy to them. While not documented well at all, it turns out that this is relatively easy to accomplish in four simple steps.

1. Determine the MAC address of your guest machine

Let's say you have a guest machine with the name ubuntu-lucid-lynx-base a

rahul100885

user deploy;
worker_processes 6;

events {
    worker_connections 1024;
}


http {
    passenger_root /usr/local/rvm/gems/ree-1.8.7-2011.03/gems/passenger-3.0.7;

sandro

require 'rubygems'
require 'httparty'
require 'benchmark'
require 'thread'

class Google
  include HTTParty
  base_uri 'http://google.com'

  def self.benchmark

rtomayko

#!/usr/bin/env ruby
#/ Usage: <progname> [options]...
#/ How does this script make my life easier?
# ** Tip: use #/ lines to define the --help usage message.
$stderr.sync = true
require 'optparse'

# default options
flag    = false
option  = "default value"

potch

.gist-highlight {
    border-left: 3ex solid #eee;
    position: relative;
}

.gist-highlight pre {
    counter-reset: linenumbers;
}

.gist-highlight pre div:before {