orats 0.2.0 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: d6bad42dd6b612594bb115996f943c6343ed6aac
-  data.tar.gz: 39d518e79e1f5ab96f67c13989e969e83dd9372b
+  metadata.gz: 0a6c0e8dbdf731aa4475b5146b8e7816d42dd9db
+  data.tar.gz: 2574c41229f58b27670a7d6caff9af1a6b4cc2a7
 SHA512:
-  metadata.gz: c80b52eb4bc604a7841b5eabacc6ddba6ac1d12404b3a96bffadec0a3e164e044445d7fc61fd450a3815a3168007706afca8ca946aec27ded2c7ac0ee0409e3b
-  data.tar.gz: 3df85308dc2ec16d8fdf5a2838605fc45110a796c25c228c13bf59fdebe25fa978a60a6d41664e6484ef9bb2e2afc31687b672b904178f0495c0a1cfcf568650
+  metadata.gz: e0629f4d2632b7697ea66880de7723762ac23714a110f770b4a221e22f7ac0d293eda935cc7e6a29b27179a3ca6dce448d1c5cdb7dfcc6d4b63e88f360c5cd3f
+  data.tar.gz: 30eaf60bafff537a7ed5931d15715addde4e548955286fedb51258e6af4135d4f71d79530933e205c947b9e4e89df0c286f3f0d2ed0455ac90a10e48fc29d1a6

data/Gemfile.lock

@@ -1,13 +1,13 @@
 PATH
   remote: .
   specs:
-    orats (0.2.0)
+    orats (0.3.0)
       thor (~> 0)
 
 GEM
   remote: https://rubygems.org/
   specs:
-    rake (10.1.1)
+    rake (0.9.6)
     thor (0.18.1)
 
 PLATFORMS
@@ -16,4 +16,4 @@ PLATFORMS
 DEPENDENCIES
   bundler (~> 1.5)
   orats!
-  rake
+  rake (~> 0)

data/README.md

@@ -1,12 +1,10 @@
 ## What is orats and what problem does it solve?
 
-It stands for opinionated rails application templates. This repository has a collection of opinionated templates
-to get you up and going with a modern rails application stack. They are accessed through the [orats gem](#installation).
+It stands for opinionated rails application templates. The templates include solving tedious tasks that you would do for most
+projects. It handles creating a rails application with a bunch of opinions and optionally a chef cookbook so you can deploy
+your app quickly.
 
-I noticed I kept making the same changes to every single rails app I made and it actually takes quite a bit of time to
-setup all of this manually each time you make an app.
-
-It is clearly a problem that can be automated so I sat down and started to create a few templates to do just that.
+Everything is accessed through the [orats gem](#installation).
 
 ## What version of Rails and Ruby are you targeting?
 
@@ -15,14 +13,14 @@ It is clearly a problem that can be automated so I sat down and started to creat
 I will be updating them as new versions come out and when the gems used are proven to work. All important gems in the Gemfile
 are locked using the pessimistic operator `~>` so you can be sure that everything plays nice as long as rubygems.org is up!
 
-## System dependencies that apply to every template
+## System dependencies that you must have on your dev box
 
 - [The orats gem](#installation)
     - To download each rails template and automate running certain tasks.
 - Ruby 2.1.x
     - Yep, you really need Ruby to run Ruby modules.
 - Rails 4.0.x
-    - You also need Rails installed so that you can run the project generator.
+    - You need Rails installed so that you can run the project generator.
 - Git
     - The weapon of choice for version control.
 - Postgres
@@ -30,19 +28,34 @@ are locked using the pessimistic operator `~>` so you can be sure that everythin
 - Redis
     - Used as a sidekiq background worker and as the rails cache back end.
 
+### Additional system dependencies for creating cookbooks
+
+`orats` is smart enough to skip trying to create a cookbook if it cannot find the necessary dependencies to successfully
+create the cookbook, but to successfully create a cookbook you must fulfil the requirements below:
+
+- Chef is installed and setup in such a way that `knife` is on your system path.
+- Berkshelf has been gem installed and you can run `berks` from anywhere.
+
+Not sure what chef or berkshelf is? No problem, learn about chef from these resources:
+
+- [Learn chef course](https://learnchef.opscode.com/)
+- [Berkshelf readme](http://www.berkshelf.com/)
+- [Berkshelf tutorial series](http://misheska.com/blog/2013/06/16/getting-started-writing-chef-cookbooks-the-berkshelf-way/)
+
 ## Contents
 
 - orats
     - [Installation](#installation)
     - [Commands](#commands)
 - Templates
-    - [Base](#base-template)
+    - [Base](#base)
     - [Authentication and authorization](#authentication-and-authorization)
-    - [Application deployment](#application-deployment)
-    - [Server provisioning](#server-provisioning)
+    - [Cookbook](#cookbook)
+        - [Overview](#the-cookbook-comes-with-the-following-features)
 - Sections
-    - [Expanding beyond the base template](#expanding-beyond-the-base-template)
     - [Production tweaks](#production-tweaks)
+- Wikis
+    - [Chef walk through](https://github.com/nickjj/orats/wiki/Chef-walk-through)
 
 ## orats
 
@@ -50,36 +63,38 @@ are locked using the pessimistic operator `~>` so you can be sure that everythin
 
 `gem install orats`
 
-
 ### Commands
 
-#### Application tasks
+Here is an overview of the available commands. You can find out more information about each command and flag by simply
+running `orats <command name> help` from your terminal. You can also type `orats` on its own to see a list of all commands.
 
-- Create a new rails application using the base template.
-    - `orats base <app name> --postgres-password <insert your development postgres db password>`
-    - Optionally takes `--postgres-location [localhost]`
-    - Optionally takes `--postgres-username [postgres]`
+- Create a new orats project
+    - `orats new <APP_PATH> --pg-password <development postgres db password>`
+    - Configuration:
+        - Optionally takes: `--pg-location [localhost]`
+        - Optionally takes: `--pg-username [postgres]`
+    - Template features:
+        - Optionally takes: `--auth [false]`
+    - Project features:
+        - Optionally takes: `--skip-cook [false]`
+        - Optionally takes: `--skip-extras [false]`
 
-- Create a new rails application with authentication/authorization.
-    - `orats auth <app name> --postgres-password <insert your development postgres db password>`
-    - Optionally takes `--postgres-location [localhost]`
-    - Optionally takes `--postgres-username [postgres]`
+- Create a stand alone chef cookbook
+    - `orats cook <APP_PATH>`
 
-- Delete an application and optionally its postgres databases and redis namespace.
-    - `orats nuke <app name>`
-    - Optionally takes `--delete-data [true]`
+- Delete the directory and optionally all data associated to it
+    - `orats nuke <APP_PATH>`
+    - Optionally takes `--skip-data [false]`
 
 #### Why is it asking me for my development postgres password?
 
-The password is it asking for is only for your development database. It will **never** ask for your production passwords.
-
 In order to automate certain tasks such as running database migrations the script must be able to talk to your database.
 It cannot talk to your database without knowing the location, username and password for postgres. In most cases the
 location will be `localhost` and the username will be `postgres` so these values are provided by default.
 
-If you are curious about the implementation details feel free to [take a look](https://github.com/nickjj/orats/blob/master/orats.thor#L127).
+Remember, this is only your development postgres password. It will **never** ask for your production passwords.
 
-## Base template
+## Base
 
 This is the starter template that every other template will append to. I feel like when I make a new project, 95% of the time
 it includes these features and when I do not want a specific thing it is much quicker to remove it than add it.
@@ -117,7 +132,20 @@ Everything has been added with proper git commits so you have a trail of changes
 
 ### Try it
 
-`orats base myapp --postgres-password <development postgres db password>`
+`orats new myapp --pg-password <development postgres db password> -C`
+
+*We are running the command with `-C` to ignore creating a cookbook so the installation is faster.*
+
+#### What's with the services directory?
+
+It is just a naming convention that I like to apply, you can name it whatever you want later or remove it with a flag. My thought
+process was you might have multiple services which when put together create your web application. In many cases your web
+application might just be a single rails app, but maybe not.
+
+What if you introduced a Go service to do something which your rails application talks to for a certain area of your site?
+Perhaps you have 2 rails applications too. One of them for your admin app and the other for the public facing app.
+
+Long story short the extra directory is probably worth it in the long run and it's simple to remove if you don't like it.
 
 ### All I see is the default rails page
 
@@ -182,18 +210,125 @@ I feel like this is the cleanest way to disable registrations while still allowi
 
 ### Try it
 
-`orats auth myapp --postgres-password <development postgres db password>`
+`orats new myauthapp --pg-password <development postgres db password> --auth -C`
+
+*We are running the command with `-C` to ignore creating a cookbook so the installation is faster.*
+
+## Cookbook
+
+Building your application is only one piece of the puzzle. If you want to ship your application you have to host it somewhere.
+You have a few options when it comes to managed hosts like Heroku but they tend to be very expensive if you fall out of
+their free tier.
+
+The cookbook template creates a chef cookbook that will provision a **ubuntu 12.04 LTS server**. It can be hosted anywhere
+as there are no hard requirements on any specific host. Chef is a server management framework. This template uses the
+application cookbook pattern and depends on Berkshelf. Berkshelf is very similar to bundler but for chef cookbooks.
+
+### The cookbook comes with the following features
+
+- Security
+    - A random username is generated each time you generate a new cookbook.
+    - A random ssh port is generated each time you generate a new cookbook.
+    - Logging into the server is only possible with an SSH key.
+    - fail2ban is setup.
+    - ufw (firewall) is setup to block any ports not exposed.
+    - All stack specific processes are running with less privileges than root.
+- Stack specific processes that are installed and configured
+    - Nginx
+    - Postgres
+    - Redis
+- Runtimes
+    - Ruby 2.1.0 managed via rvm
+    - Nodejs 0.10.x
+- Utils and features
+    - htop for emergency live monitoring
+    - logrotate with log rotation setup for anything that needs it.
+    - git
+    - A git repo in the deploy user's home directory which you can push to.
+
+### Cookbook structure
+
+It is broken up into 5 recipes:
+
+- Base
+- Database
+- Cache
+- Web
+- Default
+
+With the application style cookbook pattern it is a good idea to only run one recipe on your node. The default recipe
+just composes the other 4 together. This makes it trivial to break out past one node in the future. If you wanted to
+put your web server on server A and the database/cache servers on server B all you would have to do is create a new recipe
+called something like `database_cache` (the name is arbitrary) and pull in both the database and cache recipes.
+
+Then when you bootstrap the node you can tell it to use the new `database_cache` recipe. Awesome right? Yeah I know, chef rocks.
+
+### Try it
+
+`orats new mychefapp --pg-password <development postgres db password>`
+
+#### Why is the cookbooks directory plural?
+
+It is not uncommon for some projects to have multiple cookbooks. Of course that is completely out of scope for orats but
+at least it generates a directory structure capable of sustaining multiple cookbooks.
+
+### Tweakable attributes and meta data
+
+You can quickly tweak a bunch of values by investigating the `attributes/default.rb` file. The values here are used in each
+recipe. They are also namespaced to match the recipe file that uses them.
+
+It is important that you change all of these values to match your setup. The only non-obvious one might be the SSH key. You
+should use the key inside of your `.ssh/id_rsa.pub` file. It is the key that ends with your work station's username@hostname. Make
+sure you do not include the trailing line break too.
+
+You should also edit the details in the `metadata.rb` file.
+
+### Encrypted values
+
+Chef has this notion of encrypted data bags. They are used to protect sensitive information like passwords or secret tokens.
+You can check out the `data_bags/<app_name>_secrets/production.json` file to know which fields you need to fill out later.
+
+Please keep in mind that you should never input your real passwords/etc. in this file, it is only here to remind you which
+settings are in your bag. This file is checked into version control. We will cover setting up the data bag with your real
+information in [chef walk through on the wiki](https://github.com/nickjj/orats/wiki/Chef-walk-through).
+
+### Workflow for customizing the cookbook
+
+This cookbook is designed to be a generic base to get you started. It is highly encouraged to change the cookbook to suite your
+exact needs. A typical workflow for making changes to the cookbook is this:
+
+- Edit any files that you want to change.
+- Bump the version in the `metadata.rb` file. *Never forget to do this step!*
+- Run `berks upload` which sends the cookbooks up to your hosted chef server.
+
+If you need to add new cookbooks then add them to `metadata.rb` and run `berks install`. If you need to pull in a cookbook
+from a git repo or your local file system then put them in your `Berksfile` and also place them in `metadata.rb`. Check the
+berkshelf documentation for more details.
+
+#### Applying the cookbook changes on your server
+
+This step is highly dependent but you have a few options. The first option is to ssh into your node and run `sudo chef-client`.
+Replace ssh with capistrano if you want but the idea is the same. You would be manually invoking the `chef-client` command
+which tells your node to contact the hosted chef server and pull in the changes.
+
+The second option would be to setup a cronjob to run `chef-client` automatically at whatever interval you want. By default
+I did not include this because by default chef does not do this.
+
+Chef is idempotent so it will not re-run tasks that result in nothing changing so feel free to make changes whenever you
+see fit.
+
+### The server is up but how do I deploy my application?
 
-## Server provisioning
+This is another area where there are many options. You could use capistrano but you could also have chef manage the application
+deployment too. I have a few old capistrano 2.x scripts that work fine and I really do not have any intentions of porting
+them over to capistrano 3 scripts so they can be included as an orats template because I do not want to use capistrano anymore.
 
-I really like chef and I think at some point there might be a template which creates an application cookbook which provisions
-every dependency required to setup this stack using **ubuntu server 12.04 LTS**.
+I'm calling out to the community for help. Can a chef expert please leverage the `deploy` or `application` resources
+and provide us with a well documented solution to deploy a rails application with chef? Complete with runit scripts for
+ensuring puma and sidekiq are always running of course.
 
-I don't think it will ever get too advanced because deployment is very specific to each application but it can at least
-dump out a ~200 line cookbook that configures everything to get a server up and running and all you would have to do is
-change a few settings in the chef attributes file and setup an encrypted data bag like usual.
+### Walk through
 
-Right now I have a template in the works that will get you from an empty ubuntu server to a fully working server that
-can do everything but handle deploying your rails application. Normally I use capistrano to deploy my app but I want to
-move away from that and let chef handle it but I do not have the chef chops to do this yet. I will gladly accept any pull
-requests to add this functionality in.
+If you have very little chef experience and want to go through the steps of creating a new orats project with a cookbook,
+pushing it to a free managed chef server solution and bootstrapping a server on a local virtual machine then check out the
+[chef walk through on the wiki](https://github.com/nickjj/orats/wiki/Chef-walk-through).

data/lib/orats/cli.rb

@@ -8,78 +8,128 @@ module Orats
     include Shell
     include Server
 
-    attr_accessor :app_name, :app_name_only
+    attr_accessor :active_path, :active_project
 
-    class_option :postgres_location, default: 'localhost'
-    class_option :postgres_username, default: 'postgres'
+    option :pg_location, default: 'localhost'
+    option :pg_username, default: 'postgres'
+    option :pg_password, required: true
+    option :auth, type: :boolean, default: false, aliases: '-a'
+    option :skip_cook, type: :boolean, default: false, aliases: '-C'
+    option :skip_extras, type: :boolean, default: false, aliases: '-E'
+    desc 'new APP_PATH [options]', ''
+    long_desc <<-LONGDESC
+      `orats new myapp --pg-password supersecret` will create a new orats project and it will also create a chef cookbook to go with it by default.
 
-    option :postgres_password, required: true
-    desc 'base APP_NAME', 'Create a new rails application using the base template.'
-    def base(app_name)
-      @app_name = app_name
+      You must supply at least this flag:
 
-      run "rails new #{@app_name} --skip-bundle --template #{File.expand_path File.dirname(__FILE__)}/templates/commands/base.rb"
+      `--pg-password` to supply your development postgres password so the rails application can run database migrations
 
-      gsub_postgres_info options
-      git_commit 'Change the postgres information'
+      Configuration:
 
-      bundle_install
-      git_commit 'Add gem lock file'
+      `--pg-location` to supply a custom postgres location [localhost]
 
-      run_rake 'db:create:all db:migrate db:test:prepare'
-      git_commit 'Add the database schema file'
+      `--pg-username` to supply a custom postgres username [postgres]
 
-      foreman_start unless invoked?
-    end
+      Template features:
+
+      `--auth` will include authentication and authorization [false]
 
-    option :postgres_password, required: true
-    desc 'auth APP_NAME', 'Create a new rails application with authentication/authorization.'
-    def auth(app_name)
-      @app_name = app_name
+      Project features:
 
-      invoke :base
+      `--skip-cook` skip creating the cookbook [false]
 
-      run "rails new #{@app_name} --skip --skip-bundle --template #{File.expand_path File.dirname(__FILE__)}/templates/commands/auth.rb"
+      `--skip-extras` skip creating the services directory and cookbook [false]
+  LONGDESC
+    def new(app_name)
+      @options = options
+      @active_path = app_name
 
-      run_rake 'db:migrate db:seed'
+      @active_path = services_path(app_name)
+      rails_template 'base' do
+        gsub_postgres_info
+
+        bundle_install
+        git_commit 'Change the postgres information'
+        git_commit 'Add gem lock file'
+
+        run_rake 'db:create:all db:migrate db:test:prepare'
+        git_commit 'Add the database schema file'
+      end
+
+      if options[:auth]
+        rails_template 'auth', '--skip ' do
+          run_rake 'db:migrate db:seed'
+        end
+      end
+
+      unless options[:skip_cook] || options[:skip_extras]
+        cook_app cookbooks_path(app_name)
+      end
 
+      @active_path = services_path(app_name)
       foreman_start unless invoked?
     end
 
-    desc 'nuke APP_NAME', 'Delete an application and optionally its postgres databases and redis namespace.'
-    option :postgres_password, required: false
-    option :delete_data, type: :boolean, default: true
+    desc 'cook APP_PATH', ''
+    long_desc <<-LONGDESC
+      `orats cook myapp` will create a stand alone cookbook.
+    LONGDESC
+    def cook(app_name)
+      @options = options
+      @active_path = app_name
+
+      cook_app app_name
+    end
+
+    option :skip_data, type: :boolean, default: false, aliases: '-S'
+    desc 'nuke APP_PATH [options]', ''
+    long_desc <<-LONGDESC
+      `orats nuke myapp` will delete the directory and optionally all data associated to it.
+
+      Options:
+
+      `--skip-data` will skip deleting app specific postgres databases and redis namespaces [false]
+    LONGDESC
     def nuke(app_name)
-      @app_name = app_name
+      @active_path = app_name
 
       puts
       say_status  'nuke', "\e[1mYou are about to permanently delete this directory:\e[0m", :red
-      say_status  'path', "#{File.expand_path(app_name)}", :yellow
+      say_status  'path', "#{File.expand_path(@active_path)}", :yellow
 
-      if options[:delete_data]
+      unless options[:skip_data]
         puts
         say_status  'nuke', "\e[1mYou are about to permanently delete these postgres databases:\e[0m", :red
-        say_status  'databases', "#{app_name_only} and #{app_name_only}_test", :yellow
+        say_status  'databases', "#{active_project} and #{active_project}_test", :yellow
         puts
         say_status  'nuke', "\e[1mYou are about to permanently delete this redis namespace:\e[0m", :red
-        say_status  'namespace', app_name_only, :yellow
+        say_status  'namespace', active_project, :yellow
       end
       puts
 
       confirmed_to_delete = yes?('Are you sure? (y/N)', :cyan)
 
       if confirmed_to_delete
-        if options[:delete_data]
+        unless options[:skip_data]
           run_rake 'db:drop:all'
           nuke_redis
-          nuke_directory
         end
+
+        nuke_directory
       end
     end
 
     private
-      def app_name_only
-        @app_name.split('/').last
+      def active_project
+        @active_path.split('/').last
+      end
+
+      def services_path(app_name)
+        options[:skip_extras] ?  app_name : "#{app_name}/services/#{active_project}"
+      end
+
+      def cookbooks_path(app_name)
+        "#{app_name}/cookbooks/#{active_project}"
       end
 
       def invoked?

data/lib/orats/server.rb

@@ -6,7 +6,7 @@ module Orats
     def foreman_start
       puts  '', '='*80
       say_status  'action', "\e[1mStarting server with the following commands:\e[0m", :cyan
-      say_status  'command', "cd #{@app_name}", :magenta
+      say_status  'command', "cd #{@active_path}", :magenta
       say_status  'command', 'bundle exec foreman start', :magenta
       puts  '='*80, ''
 
@@ -25,7 +25,8 @@ module Orats
         end
 
         puts
-        run_with_cd 'bundle exec foreman start'
+
+        run_from @active_path, 'bundle exec foreman start'
       end
 
       def port_taken?

data/lib/orats/shell.rb

@@ -1,7 +1,13 @@
 module Orats
   module Shell
-    def run_with_cd(command)
-      run "cd #{@app_name} && #{command} && cd -"
+    def run_from(path, command)
+      run "cd #{path} && #{command} && cd -"
+    end
+
+    def cd_inside(path, &block)
+      run "cd #{path}"
+      yield
+      run 'cd -'
     end
 
     def log_message(type, message)
@@ -11,39 +17,105 @@ module Orats
     end
 
     def git_commit(message)
-      run_with_cd "git add . && git commit -m '#{message}'"
+      run_from @active_path, "git add . && git commit -m '#{message}'"
     end
 
-    def gsub_postgres_info(options)
+    def gsub_postgres_info
       log_message 'root', 'Changing the postgres information'
 
-      gsub_file "#{@app_name}/.env", ': localhost', ": #{options[:postgres_location]}"
-      gsub_file "#{@app_name}/.env", ': postgres', ": #{options[:postgres_username]}"
-      gsub_file "#{@app_name}/.env", ': supersecrets', ": #{options[:postgres_password]}"
+      gsub_file "#{@active_path}/.env", ': localhost', ": #{@options[:pg_location]}"
+      gsub_file "#{@active_path}/.env", ': postgres', ": #{@options[:pg_username]}"
+      gsub_file "#{@active_path}/.env", ': supersecrets', ": #{@options[:pg_password]}"
     end
 
     def run_rake(command)
       log_message 'shell', 'Running rake commands'
 
-      run_with_cd "bundle exec rake #{command}"
+      run_from @active_path, "bundle exec rake #{command}"
     end
 
     def bundle_install
       log_message 'shell', 'Running bundle install, this may take a while'
 
-      run "cd #{@app_name} && bundle install && cd -"
+      run_from @active_path, 'bundle install'
     end
 
     def nuke_redis
       log_message 'root', 'Removing redis keys'
 
-      run "redis-cli KEYS '#{@app_name_only}:*' | xargs --delim='\n' redis-cli DEL"
+      run "redis-cli KEYS '#{active_project}:*' | xargs --delim='\n' redis-cli DEL"
     end
 
     def nuke_directory
       log_message 'root', 'Deleting directory'
 
-      run "rm -rf #{@app_name}"
+      run "rm -rf #{@active_path}"
+    end
+
+    def exit_if_exists
+      log_message 'shell', 'Checking if a file or directory already exists'
+
+      if Dir.exist?(@active_path) || File.exist?(@active_path)
+        puts
+        say_status  'aborting', "\e[1mA file or directory already exists at this location:\e[0m", :red
+        say_status  'location', @active_path, :yellow
+        puts        '-'*80
+        puts
+
+        exit 1
+      end
+    end
+
+    def exit_if_cannot_cook
+      log_message 'shell', 'Checking for the cookbook system dependencies'
+
+      has_knife = run('which knife', capture: true)
+      has_berks = run('which berks', capture: true)
+
+      dependency_error 'Cannot access knife',
+                       'Are you sure you have chef setup correctly?',
+                       'http://www.getchef.com/chef/install/`' if has_knife.empty?
+
+
+      dependency_error 'Cannot access berkshelf',
+                       'Are you sure you have berkshelf installed correctly?',
+                       'You can install it by running `gem install berkshelf`' if has_berks.empty?
+    end
+
+    def exit_if_cannot_rails
+      log_message 'shell', 'Checking for rails'
+
+      has_rails = run('which rails', capture: true)
+
+      dependency_error 'Cannot access rails',
+                       'Are you sure you have rails setup correctly?',
+                       'You can install it by running `gem install rails`' if has_rails.empty?
+    end
+
+    def dependency_error(message, question, answer)
+      puts
+      say_status  'error', "\e[1m#{message}\e[0m", :red
+      say_status  'question', question, :yellow
+      say_status  'answer', answer, :cyan
+      puts        '-'*80
+      puts
+
+      exit 1
+    end
+
+    def rails_template(command, flags = '', &block)
+      exit_if_cannot_rails
+      exit_if_exists unless flags.index(/--skip /)
+
+      run "rails new #{@active_path} #{flags}--skip-bundle --template #{File.expand_path File.dirname(__FILE__)}/templates/#{command}.rb"
+      yield if block_given?
+    end
+
+    def cook_app(app_path)
+      exit_if_cannot_cook
+
+      @active_path = app_path
+      rails_template 'cook'
     end
   end
 end

data/lib/orats/templates/{commands/base.rb → base.rb}

@@ -11,7 +11,7 @@ def generate_token
 end
 
 def from_gem(source, destination = nil)
-  base_path = "#{File.expand_path File.dirname(__FILE__)}/../includes"
+  base_path = "#{File.expand_path File.dirname(__FILE__)}/includes"
   file_name = source.split('/').last
 
   if destination.present? && file_name != destination

data/lib/orats/templates/cook.rb

@@ -0,0 +1,630 @@
+# =====================================================================================================
+# Template for generating a chef cookbook
+# =====================================================================================================
+
+# ----- Helper functions and variables ----------------------------------------------------------------
+
+require 'securerandom'
+
+def generate_token
+  SecureRandom.hex(64)
+end
+
+def git_config(field)
+  command = "git config --global user.#{field}"
+  git_field_value = run(command, capture: true).gsub("\n", '')
+  default_value = "YOUR_#{field.upcase}"
+
+  git_field_value.to_s.empty? ? default_value : git_field_value
+end
+
+app_name_upper = app_name.upcase
+app_name_class = app_name.humanize
+
+author_name = git_config 'name'
+author_email = git_config 'email'
+
+# ----- Nuke all of the rails code --------------------------------------------------------------------
+
+puts
+say_status  'shell', 'Removing all of the generated rails code...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+run 'rm -rf * .git .gitignore'
+
+# ----- Install berkshelf -----------------------------------------------------------------------------
+
+puts
+say_status  'tool', 'Gem installing berkshelf, this may take a while...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+run 'gem install berkshelf'
+
+# ----- Create cookbook -------------------------------------------------------------------------------
+
+puts
+say_status  'init', 'Creating skeleton cookbook...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+run "berks cookbook #{app_name}"
+
+# ----- Move cookbook back one directory --------------------------------------------------------------
+
+puts
+say_status  'shell', 'Moving cookbook back one directory...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+run "mv #{app_name}/* ."
+run "rm -rf #{app_name}"
+
+# ----- Create the git repo ---------------------------------------------------------------------------
+
+puts
+say_status  'git', 'Creating initial commit...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+git :init
+git add: '.'
+git commit: "-m 'Initial commit'"
+
+# ----- Create the license ----------------------------------------------------------------------------
+
+puts
+say_status  'root', 'Creating the license', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+run 'rm -rf LICENSE'
+
+file 'LICENSE' do <<-TEXT
+The MIT License (MIT)
+
+Copyright (c) #{Time.now.year} #{author_name} <#{author_email}>
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+'Software'), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+TEXT
+end
+
+git add: '.'
+git commit: "-m 'Add MIT license'"
+
+# ----- Customize meta data ---------------------------------------------------------------------------
+
+puts
+say_status  'root', 'Changing metadata file', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+puts author_name
+puts author_email
+
+gsub_file 'metadata.rb', 'YOUR_NAME', author_name
+gsub_file 'metadata.rb', 'YOUR_EMAIL', author_email
+gsub_file 'metadata.rb', 'All rights reserved', 'MIT LICENSE'
+
+git add: '.'
+git commit: "-m 'Change meta data in the metadata.rb file'"
+
+# ----- Add application dependencies ------------------------------------------------------------------
+
+puts
+say_status  'root', 'Adding application dependencies...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+append_file 'Berksfile' do <<-CODE
+cookbook 'postgresql', git: 'git://github.com/phlipper/chef-postgresql.git'
+cookbook 'rvm', git: 'git://github.com/fnichol/chef-rvm'
+CODE
+end
+
+git add: '.'
+git commit: "-m 'Add dependencies to the Berksfile'"
+
+append_file 'metadata.rb' do <<-CODE
+# base
+depends 'openssh', '~> 1.3.2'
+depends 'user', '~> 0.3.0'
+depends 'sudo', '~> 2.3.0'
+depends 'fail2ban', '~> 2.1.2'
+depends 'ufw', '~> 0.7.4'
+depends 'swap', '~> 0.3.6'
+
+# database
+depends 'postgresql', '~> 0.13.0'
+
+# cache
+depends 'redisio', '~> 1.7.0'
+
+# web
+depends 'git', '~> 2.9.0'
+depends 'rvm', '~> 0.9.1'
+depends 'nodejs', '~> 1.3.0'
+depends 'nginx', '~> 2.2.0'
+depends 'logrotate', '~> 1.4.0'
+CODE
+end
+
+git add: '.'
+git commit: "-m 'Add dependencies to the metadata file'"
+
+# ----- Install cookbooks locally ---------------------------------------------------------------------
+
+puts
+say_status  'tool', 'Berks installing the cookbooks, this may take a while...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+run 'berks install'
+
+git add: '.'
+git commit: "-m 'Change meta data in the metadata.rb file'"
+
+# ----- Configure attributes file ---------------------------------------------------------------------
+
+puts
+say_status  'attr', 'Modifying the attributes file...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+random_ssh_port = rand(11000..55000)
+random_username = SecureRandom.hex[0...8]
+
+file 'attributes/default.rb' do <<-CODE
+default[:#{app_name}][:base][:ssh_port] = '#{random_ssh_port}'
+default[:#{app_name}][:base][:username] = '#{random_username}'
+default[:#{app_name}][:base][:swap_size] = 1024 # MBs
+default[:#{app_name}][:base][:ssh_key] = 'INSERT_YOUR_PUBLIC_SSH_KEY_HERE'
+
+default[:#{app_name}][:database][:host] = 'localhost'
+default[:#{app_name}][:database][:pool] = '25'
+default[:#{app_name}][:database][:timeout] = '5000'
+
+default[:#{app_name}][:cache][:host] = 'localhost'
+default[:#{app_name}][:cache][:port] = '6379'
+default[:#{app_name}][:cache][:database] = '0'
+default[:#{app_name}][:cache][:sidekiq_concurrency] = '25'
+
+default[:#{app_name}][:web][:ruby_version] = '2.1.0'
+default[:#{app_name}][:web][:puma_threads_min] = '0'
+default[:#{app_name}][:web][:puma_threads_max] = '16'
+default[:#{app_name}][:web][:puma_workers] = '2'
+default[:#{app_name}][:web][:mail_address] = 'smtp.#{app_name}.com'
+default[:#{app_name}][:web][:mail_port] = '25'
+default[:#{app_name}][:web][:mail_domain] = '#{app_name}.com'
+default[:#{app_name}][:web][:mail_username] = 'info@#{app_name}.com'
+default[:#{app_name}][:web][:mail_auth] = 'plain'
+default[:#{app_name}][:web][:mail_startttls_auto] = 'true'
+default[:#{app_name}][:web][:action_mailer_host] = 'www.#{app_name}.com'
+default[:#{app_name}][:web][:action_mailer_default_email] = 'info@#{app_name}.com'
+default[:#{app_name}][:web][:action_mailer_devise_default_email] = 'info@#{app_name}.com'
+CODE
+end
+
+git add: '.'
+git commit: "-m 'Add tweakable settings to the attributes file'"
+
+# ----- Create dummy data for the encrypted data bag --------------------------------------------------
+
+puts
+say_status  'data_bags', 'Creating dummy encrypted data bag...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+data_bag_path = "data_bags/#{app_name}_secrets"
+
+run "mkdir -p #{data_bag_path}"
+
+file "#{data_bag_path}/production.json" do <<-JSON
+{
+  "id": "production",
+  "database_password": "<real password is protected>",
+  "cache_password": "<real password is protected>",
+  "mail_password": "<real password is protected>",
+  "token_rails_secret": "<real token is protected>",
+  "token_devise_secret": "<real token is protected>",
+  "token_devise_pepper": "<real token is protected>"
+}
+JSON
+end
+
+git add: '.'
+git commit: "-m 'Add the dummy data bag as a point of reference'"
+
+# ----- Create nginx config ---------------------------------------------------------------------------
+
+puts
+say_status  'files', 'Creating nginx config...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+file "files/default/nginx_virtualhost.conf" do <<-CONF
+upstream #{app_name} {
+  server unix:///tmp/#{app_name}.sock;
+}
+
+# redirect non-www to www (remove this block if you do not want to do this)
+server {
+  listen 80;
+  server_name #{app_name}.com;
+  return 301 $scheme://www.#{app_name}.com$request_uri;
+}
+
+server {
+  listen 80;
+  server_name www.#{app_name}.com;
+  root /home/#{random_username}/www/#{app_name}/current/public;
+
+  error_page 404 /404.html;
+  error_page 500 /500.html;
+  error_page 502 503 504 /502.html;
+
+  location ~ ^/(system|assets)/ {
+    root /home/#{random_username}/www/#{app_name}/current/public;
+    gzip_static on;
+    expires 1y;
+    add_header Cache-Control public;
+    add_header ETag "";
+    break;
+  }
+
+  try_files $uri @puma;
+
+  location @puma {
+    proxy_set_header X-Real-IP $remote_addr;
+    proxy_set_header X-Forwarded-Proto http;
+    proxy_set_header Host $http_host;
+    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+    proxy_redirect off;
+
+    proxy_pass http://#{app_name};
+    break;
+  }
+}
+CONF
+end
+
+git add: '.'
+git commit: "-m 'Add the nginx virtualhost config'"
+
+# ----- Create system wide profile -------------------------------------------------------------------------
+
+puts
+say_status  'templates', 'Creating system wide profile config', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+file 'templates/default/profile.erb' do <<-CONF
+# /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
+# and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).
+
+if [ "$PS1" ]; then
+  if [ "$BASH" ] && [ "$BASH" != "/bin/sh" ]; then
+    # The file bash.bashrc already sets the default PS1.
+    # PS1='\h:\w\$ '
+    if [ -f /etc/bash.bashrc ]; then
+      . /etc/bash.bashrc
+    fi
+  else
+    if [ "`id -u`" -eq 0 ]; then
+      PS1='# '
+    else
+      PS1='$ '
+    fi
+  fi
+fi
+
+# The default umask is now handled by pam_umask.
+# See pam_umask(8) and /etc/login.defs.
+
+if [ -d /etc/profile.d ]; then
+  for i in /etc/profile.d/*.sh; do
+    if [ -r $i ]; then
+      . $i
+    fi
+  done
+  unset i
+fi
+
+export <%= @cookbook_name.upcase %>_TOKEN_RAILS_SECRET='<%= @token_rails_secret %>'
+export <%= @cookbook_name.upcase %>_TOKEN_DEVISE_SECRET='<%= @token_devise_secret %>'
+export <%= @cookbook_name.upcase %>_TOKEN_DEVISE_PEPPER='<%= @token_devise_pepper %>'
+
+export <%= @cookbook_name.upcase %>_SMTP_ADDRESS='<%= node[:#{app_name}][:web][:mail_address] %>'
+export <%= @cookbook_name.upcase %>_SMTP_PORT='<%= node[:#{app_name}][:web][:mail_port] %>'
+export <%= @cookbook_name.upcase %>_SMTP_DOMAIN='<%= node[:#{app_name}][:web][:mail_domain] %>'
+export <%= @cookbook_name.upcase %>_SMTP_USERNAME='<%= node[:#{app_name}][:web][:mail_username] %>'
+export <%= @cookbook_name.upcase %>_SMTP_PASSWORD='<%= @mail_password %>'
+export <%= @cookbook_name.upcase %>_SMTP_AUTH='<%= node[:#{app_name}][:web][:mail_auth] %>'
+export <%= @cookbook_name.upcase %>_SMTP_STARTTTLS_AUTO='<%= node[:#{app_name}][:web][:mail_startttls_auto] %>'
+
+export <%= @cookbook_name.upcase %>_ACTION_MAILER_HOST='<%= node[:#{app_name}][:web][:action_mailer_host] %>'
+export <%= @cookbook_name.upcase %>_ACTION_MAILER_DEFAULT_EMAIL='<%= node[:#{app_name}][:web][:action_mailer_default_email] %>'
+export <%= @cookbook_name.upcase %>_ACTION_MAILER_DEVISE_DEFAULT_EMAIL='<%= node[:#{app_name}][:web][:action_mailer_devise_default_email] %>'
+
+export <%= @cookbook_name.upcase %>_DATABASE_HOST='<%= node[:#{app_name}][:database][:host] %>'
+export <%= @cookbook_name.upcase %>_DATABASE_NAME='<%= @cookbook_name.downcase %>'
+export <%= @cookbook_name.upcase %>_DATABASE_USERNAME='postgres'
+export <%= @cookbook_name.upcase %>_DATABASE_PASSWORD='<%= @database_password %>'
+export <%= @cookbook_name.upcase %>_DATABASE_POOL='<%= node[:#{app_name}][:database][:pool] %>'
+export <%= @cookbook_name.upcase %>_DATABASE_TIMEOUT='<%= node[:#{app_name}][:database][:timeout] %>'
+
+export <%= @cookbook_name.upcase %>_CACHE_HOST='<%= node[:#{app_name}][:cache][:host] %>'
+export <%= @cookbook_name.upcase %>_CACHE_DATABASE='<%= node[:#{app_name}][:cache][:database] %>'
+export <%= @cookbook_name.upcase %>_CACHE_USERNAME='redis'
+export <%= @cookbook_name.upcase %>_CACHE_PASSWORD='<%= @cache_password %>'
+
+export <%= @cookbook_name.upcase %>_SIDEKIQ_CONCURRENCY='<%= node[:#{app_name}][:cache][:sidekiq_concurrency] %>'
+
+export <%= @cookbook_name.upcase %>_PUMA_THREADS_MIN='<%= node[:#{app_name}][:web][:puma_threads_min] %>'
+export <%= @cookbook_name.upcase %>_PUMA_THREADS_MAX='<%= node[:#{app_name}][:web][:puma_threads_max] %>'
+export <%= @cookbook_name.upcase %>_PUMA_WORKERS='<%= node[:#{app_name}][:web][:puma_workers] %>'
+CONF
+end
+
+git add: '.'
+git commit: "-m 'Add the system wide profile config'"
+
+# ----- Create base recipe ----------------------------------------------------------------------------
+
+puts
+say_status  'recipes', 'Creating base recipe...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+file 'recipes/base.rb' do <<-'CODE'
+# openssh
+
+node.override[:openssh][:server][:port] = node[:app_name][:base][:ssh_port]
+node.override[:openssh][:server][:password_authentication] = 'no'
+node.override[:openssh][:server][:permit_root_login] = 'no'
+include_recipe 'openssh'
+
+# user
+
+include_recipe 'user'
+
+user_account node[:app_name][:base][:username] do
+  ssh_keys [ node[:app_name][:base][:ssh_key] ]
+end
+
+# sudo
+
+node.override[:authorization][:sudo][:users] = [ node[:app_name][:base][:username] ]
+node.override[:authorization][:sudo][:passwordless] = true
+
+include_recipe 'sudo'
+
+# fail2ban
+
+include_recipe 'fail2ban'
+
+# ufw
+
+node.override[:firewall][:rules] = [
+  {
+    'ssh' => {
+      'port'=> node[:app_name][:base][:ssh_port]
+    }
+  },
+  {
+    'http' => {
+      'port'=> '80'
+    }
+  }
+]
+include_recipe 'ufw'
+
+# swapfile
+swap_file '/mnt/swap' do
+  size node[:app_name][:base][:swap_size]
+end
+
+# htop
+package 'htop'
+CODE
+end
+
+gsub_file 'recipes/base.rb', 'app_name', app_name
+
+git add: '.'
+git commit: "-m 'Add the base recipe'"
+
+# ----- Create database recipe ------------------------------------------------------------------------
+
+puts
+say_status  'recipes', 'Creating database recipe...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+file 'recipes/database.rb' do <<-CODE
+# This is where you will store a copy of your key on the chef-client
+secret = Chef::EncryptedDataBagItem.load_secret('/etc/chef/encrypted_data_bag_secret')
+
+# This decrypts the data bag contents of "#{app_name}_secrets/production.json" and uses the key defined at variable "secret"
+encrypted_data_bag = Chef::EncryptedDataBagItem.load('#{app_name}_secrets', 'production', secret)
+
+include_recipe '#{app_name}::base'
+include_recipe 'postgresql'
+include_recipe 'postgresql::client'
+include_recipe 'postgresql::server'
+include_recipe 'postgresql::libpq'
+
+pg_user 'postgres' do
+  privileges superuser: true, createdb: true, login: true
+  password encrypted_data_bag['database_password']
+end
+CODE
+end
+
+git add: '.'
+git commit: "-m 'Add the database recipe'"
+
+# ----- Create cache recipe ---------------------------------------------------------------------------
+
+puts
+say_status  'recipes', 'Creating cache recipe...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+file 'recipes/cache.rb' do <<-CODE
+include_recipe '#{app_name}::base'
+
+node.override[:redisio][:mirror] = 'http://download.redis.io/releases'
+node.override[:redisio][:version] = '2.8.3'
+include_recipe 'redisio::install'
+include_recipe 'redisio::enable'
+CODE
+end
+
+git add: '.'
+git commit: "-m 'Add the cache recipe'"
+
+# ----- Create web recipe -----------------------------------------------------------------------------
+
+puts
+say_status  'recipes', 'Creating web recipe...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+file 'recipes/web.rb' do <<-'CODE'
+secret = Chef::EncryptedDataBagItem.load_secret('/etc/chef/encrypted_data_bag_secret')
+encrypted_data_bag = Chef::EncryptedDataBagItem.load('app_name_secrets', 'production', secret)
+
+include_recipe 'app_name::base'
+
+# environment variables
+
+template '/etc/profile' do
+  source 'profile.erb'
+  variables({
+    :cookbook_name => cookbook_name,
+    :database_password => encrypted_data_bag['database_password'],
+    :cache_password => encrypted_data_bag['cache_password'],
+    :mail_password => encrypted_data_bag['mail_password'],
+    :token_rails_secret => encrypted_data_bag['token_rails_secret'],
+    :token_devise_secret => encrypted_data_bag['token_devise_secret'],
+    :token_devise_pepper => encrypted_data_bag['token_devise_pepper']
+  })
+end
+
+# git
+
+apt_repository 'git' do
+  uri          'http://ppa.launchpad.net/git-core/ppa/ubuntu'
+  distribution node[:lsb][:codename]
+  components   %w[main]
+  keyserver    'keyserver.ubuntu.com'
+  key          'E1DF1F24'
+  action       :add
+end
+
+include_recipe 'git'
+
+repo_path = "/home/#{node[:app_name][:base][:username]}/#{cookbook_name}.git"
+
+directory repo_path do
+  owner node[:app_name][:base][:username]
+  group node[:app_name][:base][:username]
+  mode 0755
+end
+
+execute 'initialize new bare git repo' do
+  user node[:app_name][:base][:username]
+  group node[:app_name][:base][:username]
+  command "cd #{repo_path} && git init --bare"
+  only_if { !File.exists? "#{repo_path}/HEAD" }
+end
+
+# node
+
+node.override[:nodejs][:install_method] = 'binary'
+node.override[:nodejs][:version] = '0.10.24'
+node.override[:nodejs][:checksum] = 'fb6487e72d953451d55e28319c446151c1812ed21919168b82ab1664088ecf46'
+node.override[:nodejs][:checksum_linux_x64] = '423018f6a60b18d0dddf3007c325e0cc8cf55099'
+node.override[:nodejs][:checksum_linux_x86] = 'fb6487e72d953451d55e28319c446151c1812ed21919168b82ab1664088ecf46'
+include_recipe 'nodejs::install_from_binary'
+
+# ruby
+
+node.override[:rvm][:default_ruby] = node[:app_name][:web][:ruby_version]
+node.override[:rvm][:global_gems] = [ { 'name' => 'bundler', 'version' => '1.5.1' } ]
+node.override[:rvm][:group_users] = [ node[:app_name][:base][:username] ]
+
+include_recipe 'rvm::system'
+
+# nginx
+
+apt_repository 'nginx' do
+  uri          'http://ppa.launchpad.net/nginx/stable/ubuntu'
+  distribution node[:lsb][:codename]
+  components   %w[main]
+  keyserver    'keyserver.ubuntu.com'
+  key          'C300EE8C'
+  action       :add
+end
+
+node.override[:nginx][:gzip_comp_level] = '4'
+
+include_recipe 'nginx'
+
+cookbook_file 'nginx_virtualhost.conf' do
+  path "#{node[:nginx][:dir]}/sites-available/#{cookbook_name}.conf"
+  group node[:nginx][:user]
+  owner node[:nginx][:user]
+  mode '0644'
+end
+
+nginx_site "#{cookbook_name}.conf"
+
+include_recipe 'logrotate'
+
+logrotate_app 'nginx' do
+  cookbook 'logrotate'
+  path ["#{node[:nginx][:log_dir]}/access.log", "#{node[:nginx][:log_dir]}/error.log"]
+  options ['missingok', 'notifempty']
+  frequency 'daily'
+  create '0644 root adm'
+  rotate 365
+end
+CODE
+end
+
+gsub_file 'recipes/web.rb', 'app_name', app_name
+
+git add: '.'
+git commit: "-m 'Add the web recipe'"
+
+# ----- Create default recipe -------------------------------------------------------------------------
+
+puts
+say_status  'recipes', 'Creating default recipe...', :yellow
+puts        '-'*80, ''; sleep 0.25
+
+run 'rm -f recipes/default.rb'
+file 'recipes/default.rb' do <<-CODE
+include_recipe '#{app_name}::database'
+include_recipe '#{app_name}::cache'
+include_recipe '#{app_name}::web'
+CODE
+end
+
+git add: '.'
+git commit: "-m 'Add the default recipe'"
+
+# ----- Installation complete message -----------------------------------------------------------------
+
+puts
+say_status  'success', "\e[1m\Everything has been setup successfully\e[0m", :cyan
+puts
+say_status  'question', 'Are you new to chef and berkshelf?', :yellow
+say_status  'answer', 'Check the orats wiki for the walk through', :white
+puts
+say_status  'question', 'Are you somewhat experienced with chef?', :yellow
+say_status  'answer', 'Setup your encrypted data bag and bootstrap the node', :white
+puts        '-'*80

data/lib/orats/version.rb

@@ -1,3 +1,3 @@
 module Orats
-  VERSION = '0.2.0'
+  VERSION = '0.3.0'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: orats
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.3.0
 platform: ruby
 authors:
 - Nick Janetakis
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-02-11 00:00:00.000000000 Z
+date: 2014-02-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: thor
@@ -72,8 +72,9 @@ files:
 - lib/orats/cli.rb
 - lib/orats/server.rb
 - lib/orats/shell.rb
-- lib/orats/templates/commands/auth.rb
-- lib/orats/templates/commands/base.rb
+- lib/orats/templates/auth.rb
+- lib/orats/templates/base.rb
+- lib/orats/templates/cook.rb
 - lib/orats/templates/includes/Gemfile
 - lib/orats/version.rb
 - orats.gemspec