kompanee-recipes 0.1.2 → 0.1.3

data/README.md

@@ -2,34 +2,34 @@
 
 [http://github.com/thekompanee/kompanee-recipes](http://github.com/thekompanee/kompanee-recipes)
 
-## Description ##
+## DESCRIPTION ##
 
 These are the common recipes we've been using here at The Kompanee.  Packaged as a gem.
 
-## Features/Problems ##
+## FEATURES/PROBLEMS ##
 
 None yet
 
-## Synopsis ##
+## SYNOPSIS ##
 
 To the top of your Capfile add:
 
     require 'rubygems'  
     require 'kompanee-recipes/deploy'
 
-## Requirements ##
+## REQUIREMENTS ##
 
 Capistrano (Obv)
 
-## Install ##
+## INSTALL ##
 
     gem install kompanee-recipes
 
-## Usage ##
+## USAGE ##
 
 ### New Server Setup ###
 
-#### Initial Connection ####
+#### initial connection ####
 You need to add the server to your hosts file so you'll want to do an
 initial SSH connection before we get into our Capistrano configuration.
 
@@ -37,19 +37,19 @@ initial SSH connection before we get into our Capistrano configuration.
 
 Accept the authenticity of the host.
 
-#### User Creation ####
+#### user creation ####
 By default, the Kompanee recipes will install a `deploy` user and a
 `manager` user.
 
 ##### Installation #####
     cap <environment> os:users:create
 
-##### Manual Steps As `Root` #####
+##### Manual Steps As Root #####
 Log in as `root`
 
     ssh root@<server_name>
 
-###### Password Assignment ######
+##### Password Assignment #####
 Log in to each of these and give them their custom passwords.  On
 Ubuntu this is done by loggin in as root and typing:
 
@@ -61,7 +61,7 @@ something more secure as well.
 
     passwd
 
-###### Sudo Assignment ######
+##### Sudo Assignment #####
 Finally, let's add the `manager` user to the `sudoers` file so we
 no longer need to log in as `root`
 
@@ -77,17 +77,17 @@ And a line like this:
 
 From the documentation:
 
-**visiblepw**  
-By default, sudo will refuse to run if the user must enter
-a password but it is not possible to disable echo on the
-terminal. If the `visiblepw` flag is set, sudo will prompt
-for a password even when it would be visible on the screen.
-This makes it possible to run things like:  
+> **visiblepw**  
+> By default, sudo will refuse to run if the user must enter
+> a password but it is not possible to disable echo on the
+> terminal. If the `visiblepw` flag is set, sudo will prompt
+> for a password even when it would be visible on the screen.
+> This makes it possible to run things like:  
 
-    rsh somehost sudo ls  
+>     rsh somehost sudo ls  
 
-since rsh(1) does not allocate a tty. This flag is off by
-default.
+> since rsh(1) does not allocate a tty. This flag is off by
+> default.
 
 ##### Authorize Public Key #####
 Once that's finished, go back to Capistrano and type:
@@ -96,25 +96,25 @@ Once that's finished, go back to Capistrano and type:
 
 That will give you the ability to log into your accounts with no password required.
 
-#### Note on Using Github ####
-If you're using Github to deploy your app, you're going to need to add the
-public key of the deployment user to your Github account.
+> #### note on using github ####
+> If you're using Github to deploy your app, you're going to need to add the
+> public key of the deployment user to your Github account.
 
-    cap <environment> os:users:deploy:public_key:create
+>     cap <environment> os:users:deploy:public_key:create
 
-View the public key by logging in as `deploy` and typing:
+> View the public key by logging in as `deploy` and typing:
 
-    cat /home/deploy/.ssh/id_rsa.pub
+>     cat /home/deploy/.ssh/id_rsa.pub
 
-Copy and paste the output into Github's "Public Keys" section of the Github at:
+> Copy and paste the output into Github's "Public Keys" section of the Github at:
 
-[https://github.com/account](https://github.com/account)
+>   * [https://github.com/account](https://github.com/account)
 
-Log in as `deploy` and test it out by typing:
+> Log in as `deploy` and test it out by typing:
 
-    ssh git@github.com
+>     ssh git@github.com
 
-#### Setup Deployment Server ####
+#### setup deployment server ####
 Now that we have our public keys installed, we can do a relatively simple installation.
 
     cap <environment> server_setup
@@ -126,7 +126,7 @@ a `production` task in the application's `deploy.rb` file.
 This will allow you to set specific environment variables for your application
 and stage.
 
-#### Shared Configuration Files ####
+#### shared configuration files ####
 Shared configuration files should be added to your local machine but not committed to
 source control.
 
@@ -138,7 +138,7 @@ sensitive production logins.
 When you deploy, if you have a file that meets these requirements, it will be copied
 to the proper location on the server.
 
-#### Initial Deployment ####
+#### initial deployment ####
 In order to perform the initial deployment, type:
 
     cap <environment> deploy:initial
@@ -156,7 +156,7 @@ This will:
   * Enables the website
   * Restarts the server
 
-## License ##
+## LICENSE ##
 
 (The MIT License)
 

data/lib/kompanee-recipes/bundler.rb

@@ -18,7 +18,7 @@ Capistrano::Configuration.instance(:must_exist).load do
   namespace :bundler do
     desc "Install Bundler"
     task :install do
-      run "rvm use #{default_ruby_version}@global && gem install bundler --version #{bundler_version} --no-ri --no-rdoc"
+      run "rvm use #{app_ruby_version}@global && gem install bundler --version #{bundler_version} --no-ri --no-rdoc"
     end
   end
 end

data/lib/kompanee-recipes/deploy.rb

@@ -51,6 +51,7 @@ Capistrano::Configuration.instance(:must_exist).load do
         deploy.setup
         db.create
         website.install
+        bundler.install
         deploy.cold
         deploy.check
       end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: kompanee-recipes
 version: !ruby/object:Gem::Version 
-  hash: 31
+  hash: 29
   prerelease: false
   segments: 
   - 0
   - 1
-  - 2
-  version: 0.1.2
+  - 3
+  version: 0.1.3
 platform: ruby
 authors: 
 - The Kompanee