chrislerum

cap deploy
  * executing `deploy'
  * executing `deploy:update'
 ** transaction: start
  * executing `deploy:update_code'
    updating the cached checkout on all servers
    executing locally: "git ls-remote git@github.com:chrislerum/sempermed.git master"
    command finished in 1519ms
  * executing "if [ -d ~/sites/sempermed/shared/cached-copy ]; then cd ~/sites/sempermed/shared/cached-copy && git fetch -q origin && git fetch --tags -q origin && git reset -q --hard 19646cdab9e22380d626719864e138f0eff7eeaa && git clean -q -d -x -f; else git clone -q git@github.com:chrislerum/sempermed.git ~/sites/sempermed/shared/cached-copy && cd ~/sites/sempermed/shared/cached-copy && git checkout -q -b deploy 19646cdab9e22380d626719864e138f0eff7eeaa; fi"
    servers: ["184.168.90.42"]

chrislerum

 ~/chef-repo master
knife bootstrap 33.333.333.33 --distro ubuntu10.04-gems
INFO: Bootstrapping Chef on 
WARN: Failed to connect to 33.333.333.33 -- Net::SSH::AuthenticationFailed: root@33.333.333.33

chrislerum

ruby-1.9.2-p136 ~/code/chef-repo master
chef-client
[Tue, 08 Feb 2011 10:45:31 -0500] FATAL: Failed to read the private key /etc/chef/client.pem: #<Errno::EACCES: Permission denied - /etc/chef/client.pem>, ["/Users/chris/.rvm/gems/ruby-1.9.2-p136/gems/chef-0.9.12/lib/chef/rest/auth_credentials.rb:59:in `read'", "/Users/chris/.rvm/gems/ruby-1.9.2-p136/gems/chef-0.9.12/lib/chef/rest/auth_credentials.rb:59:in `load_signing_key'", "/Users/chris/.rvm/gems/ruby-1.9.2-p136/gems/chef-0.9.12/lib/chef/rest/auth_credentials.rb:33:in `initialize'", "/Users/chris/.rvm/gems/ruby-1.9.2-p136/gems/chef-0.9.12/lib/chef/rest.rb:48:in `new'", "/Users/chris/.rvm/gems/ruby-1.9.2-p136/gems/chef-0.9.12/lib/chef/rest.rb:48:in `initialize'", "/Users/chris/.rvm/gems/ruby-1.9.2-p136/gems/chef-0.9.12/lib/chef/client.rb:243:in `new'", "/Users/chris/.rvm/gems/ruby-1.9.2-p136/gems/chef-0.9.12/lib/chef/client.rb:243:in `register'", "/Users/chris/.rvm/gems/ruby-1.9.2-p136/gems/chef-0.9.12/lib/chef/client.rb:144:in `run'", "/Users/chris/.rvm/g

chrislerum

  1 require 'formula'
  2 
  3 class Vim <Formula
  4   # Get stable versions from hg repo instead of downloading an increasing
  5   # number of separate patches.
  6   url 'https://vim.googlecode.com/hg/', :revision => '538cd32208'
  7   version '7.3.011'
  8   homepage 'http://www.vim.org/'
  9 
 10   head 'https://vim.googlecode.com/hg/'

chrislerum

ActiveRecord::Base.establish_connection(
  :adapter => "mysql",
  :user => "root",
  :password => "",
  :database => "arvest"
)


class Employee < ActiveRecord::Base
end

chrislerum

require 'rubygems'
require 'active_record'
require 'active_support'

#require_relative '/data/database.rb'

ActiveRecord::Base.establish_connection(
  :adapter => "mysql",
  :user => "root",
  :password => "",

chrislerum

  And I am on that company's page
    Then I should see the issues table
     | Issue                                 |
     | ENVIRONMENT                           |
     | Sustainability Research & Development |
     | Conservation & Waste Management       |
     | SOCIETY                               |
     | Reporting & Disclosure                |

chrislerum

ruby-1.9.2-p0@chrislerum ~ 
rvm list gemsets

rvm gemsets

   ruby-1.8.7-p174 [ x86_64 ]
   ruby-1.8.7-p174@global [ x86_64 ]
   ruby-1.8.7-p174@wastedad [ x86_64 ]
   ruby-1.8.7-p302 [ x86_64 ]
   ruby-1.8.7-p302@carpark [ x86_64 ]

chrislerum

one two three

chrislerum

Code changes should only be pushed to github if all tests are green.


Below is a common work-flow for a team working with a central repo. several variations are possible, but if unsure, please go by this:

   1. if you are working from a Pivotal Tracker story, click "start" on that story
   2. git pull (or, if this is your first time ever getting the code, do git clone git@github.com:our_repo/our_repo.git to get a local copy of the repo)
   3. rake db:migrate
   4. rake db:test:prepare
   5. spec spec