Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Added Gemfile to allow easier install of the requisite gems. #2

Open
wants to merge 1 commit into from

1 participant

@vidluther

We've been using Capistrano for deployments for a while, so wanted to see if we could merge some efforts.

Starting things off with a slightly different markup for the README.md (to allow list formatting)
Added Gemfile so people can just do bundle install now.. should make for less copy/pasting.
Added some gems we use internally for passwords, and team communication that may be useful for others in the long run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Jul 7, 2012
  1. @vidluther

    Added Gemfile for Bundler

    vidluther authored
This page is out of date. Refresh to see the latest.
Showing with 90 additions and 8 deletions.
  1. +19 −0 Gemfile
  2. +61 −0 Gemfile.lock
  3. +10 −8 README.md
View
19 Gemfile
@@ -0,0 +1,19 @@
+source 'http://rubygems.org'
+
+gem 'haddock'
+gem 'json'
+gem 'shared-secret-authentication'
+gem 'addressable'
+
+group :deployment do
+ gem 'hipchat'
+ gem 'capistrano'
+ gem 'capistrano-ext'
+ gem 'railsless-deploy'
+end
+
+group :test do
+ gem 'rspec'
+ gem 'webmock'
+ gem 'vcr'
+end
View
61 Gemfile.lock
@@ -0,0 +1,61 @@
+GEM
+ remote: http://rubygems.org/
+ specs:
+ addressable (2.2.8)
+ capistrano (2.12.0)
+ highline
+ net-scp (>= 1.0.0)
+ net-sftp (>= 2.0.0)
+ net-ssh (>= 2.0.14)
+ net-ssh-gateway (>= 1.1.0)
+ capistrano-ext (1.2.1)
+ capistrano (>= 1.0.0)
+ crack (0.3.1)
+ diff-lcs (1.1.3)
+ haddock (0.2.2)
+ highline (1.6.13)
+ hipchat (0.4.1)
+ httparty
+ httparty (0.8.3)
+ multi_json (~> 1.0)
+ multi_xml
+ json (1.7.3)
+ multi_json (1.3.6)
+ multi_xml (0.5.1)
+ net-scp (1.0.4)
+ net-ssh (>= 1.99.1)
+ net-sftp (2.0.5)
+ net-ssh (>= 2.0.9)
+ net-ssh (2.5.2)
+ net-ssh-gateway (1.1.0)
+ net-ssh (>= 1.99.1)
+ railsless-deploy (1.0.2)
+ rspec (2.10.0)
+ rspec-core (~> 2.10.0)
+ rspec-expectations (~> 2.10.0)
+ rspec-mocks (~> 2.10.0)
+ rspec-core (2.10.1)
+ rspec-expectations (2.10.0)
+ diff-lcs (~> 1.1.3)
+ rspec-mocks (2.10.1)
+ shared-secret-authentication (0.2.0)
+ vcr (2.2.2)
+ webmock (1.8.7)
+ addressable (>= 2.2.7)
+ crack (>= 0.1.7)
+
+PLATFORMS
+ ruby
+
+DEPENDENCIES
+ addressable
+ capistrano
+ capistrano-ext
+ haddock
+ hipchat
+ json
+ railsless-deploy
+ rspec
+ shared-secret-authentication
+ vcr
+ webmock
View
18 README.md
@@ -49,17 +49,19 @@ Capistrano is a code deployment tool. When you have code that is ready to go "li
1. Create a `deploy` user on your system (Ubuntu: `addgroup deploy; adduser --system --shell /bin/bash --ingroup deploy --disabled-password --home /home/deploy deploy
`).
-2. Create an SSH key for `deploy`, make sure it can SSH to all of your web servers, and make sure it can pull down your site repo code.
+1. Create an SSH key for `deploy`, make sure it can SSH to all of your web servers, and make sure it can pull down your site repo code.
* Switch to the deploy user (`su deploy`).
* `ssh-keygen`
* `cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys`
* Add the contends of `~/.ssh/id_rsa.pub` to `~/.ssh/authorized_keys` on every server you're deploying to.
-3. [Install RubyGems][rubygems].
-4. Install Capistrano and friends: `sudo gem install capistrano capistrano-ext railsless-deploy`
-5. Switch to the deploy user (`su deploy`) and check out WP Stack somewhere on your server: `git clone git@github.com:markjaquith/WP-Stack.git ~/deploy`
-6. Customize and rename `config/SAMPLE.{config|production|staging}.rb`
-7. Make sure your `:deploy_to` path exists and is owned by the deploy user: `chown -R deploy:deploy /path/to/your/deployment`
-8. Run `cap deploy:setup` (from your WP Stack directory) to setup the initial `shared` and `releases` directories.
+1. [Install RubyGems][rubygems].
+1. Install bundler (sudo gem install bundler)
+1. sudo bundle install
+1. Install Capistrano and friends: `sudo gem install capistrano capistrano-ext railsless-deploy`
+1. Switch to the deploy user (`su deploy`) and check out WP Stack somewhere on your server: `git clone git@github.com:markjaquith/WP-Stack.git ~/deploy`
+1. Customize and rename `config/SAMPLE.{config|production|staging}.rb`
+1. Make sure your `:deploy_to` path exists and is owned by the deploy user: `chown -R deploy:deploy /path/to/your/deployment`
+1. Run `cap deploy:setup` (from your WP Stack directory) to setup the initial `shared` and `releases` directories.
[rubygems]: http://rubygems.org/pages/download
@@ -92,4 +94,4 @@ If you're not using [WordPress Skeleton](https://github.com/markjaquith/WordPres
* `%%DB_USER%%` — Database username.
* `%%DB_PASSWORD%%` — Database password.
* `%%WP_STAGE%%` – will be `production` or `staging` after deploy.
-3. WP Stack uses the constants `WP_STAGE` (which should be set to `'%%WP_STAGE%%'`) and `STAGING_DOMAIN`, which should be set to the domain you want to use for staging (something like `staging.example.com`).
+3. WP Stack uses the constants `WP_STAGE` (which should be set to `'%%WP_STAGE%%'`) and `STAGING_DOMAIN`, which should be set to the domain you want to use for staging (something like `staging.example.com`).
Something went wrong with that request. Please try again.