orats 0.7.3 → 0.8.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 93556f428c47b927511dad2d9bc4581f08512abe
-  data.tar.gz: f20bb7f697ce51209756d7ab10274f5df982847d
+  metadata.gz: 5764fae3d75aa46b816aa3267b9f04da946ed458
+  data.tar.gz: ed8c551ef377131ddf6ee19b28fe231813a5bc6e
 SHA512:
-  metadata.gz: 7c17135f4b66475105a0226cca3c8431155e6e776ed517655d3dccb4f71bd9b7f27099624d51352009eaf23e6aa24b032b28c1a620f34c9e9db59ce892a69aa7
-  data.tar.gz: 79546ec90a891606628f65699c0d5cb6d82f638252a095fcd801bb5c7578f267fcaee1830ab0743dc879a0d9c292bcb1699287870fb34bf57b1ff2498624882f
+  metadata.gz: 72b68d0ca30428c544d59d150057cf9fa987cec678c22a80dee8c90b7a0e3afc730d8e06c84e4b51b888e018110d36502e178ab170965a2d2f83c04b78796d9e
+  data.tar.gz: 2dd3ab36868fd5334f9ba9059b99d250ec063ee8fc64aa027289f640bfacf00d80027918a93194fafbad2410caf2f9a01860455030e136df14754679f13aa17c

data/.gitignore

@@ -5,4 +5,5 @@
 *~
 .idea/
 *.gem
-Gemfile.lock
+Gemfile.lock
+.rubocop.yml

data/Gemfile

@@ -1,3 +1,3 @@
 source 'https://rubygems.org'
 
-gemspec
+gemspec

data/{LICENSE.txt → LICENSE}

@@ -1,22 +1,22 @@
-The MIT License (MIT)
-
-Copyright (c) 2014 Nick Janetakis <nick.janetakis@gmail.com>
-
-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
+The MIT License (MIT)
+
+Copyright (c) 2014 Nick Janetakis <nick.janetakis@gmail.com>
+
+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.

data/README.md

@@ -1,11 +1,8 @@
 [![Gem Version](https://badge.fury.io/rb/orats.png)](http://badge.fury.io/rb/orats)
 
-##### Note
-This readme file is based off the master version of orats. If you want accurate documentation then make sure to select the branch for the latest *gem version* of orats.
-
 ## What is orats and what problem does it solve?
 
-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 an ansible inventory/playbook so you can provision your servers and deploy your apps effortlessly.
+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 best practices.
 
 ## What version of Rails and Ruby are you targeting?
 
@@ -17,39 +14,24 @@ Gems will also be updated once they are proven to work on the target rails/ruby
 - [System dependencies](#system-dependencies)
 - [Installation](#installation)
 - [Commands](#commands)
-    - [Project](#project)
-    - [Inventory](#inventory)
-        - [Try it](#try-the-inventory-command)
-    - [Playbook](#playbook)
-        - [Try it](#try-the-playbook-command)
-        - [Ansible roles](#ansible-roles-used)
-        - [FAQ](#playbook-faq)
-            - [What is the Galaxyfile?](#what-is-the-galaxyfile)
-    - [Role](#role)
-        - [Try it](#try-the-role-command)
-    - [Diff](#diff)
-        - [Try it](#try-the-diff-command)
+    - [New](#new)
+        - [Try it](#try-the-new-command)
+    - [Nuke](#nuke)
+        - [Try it](#try-the-nuke-command)
     - [Templates](#templates)
         - [Try it](#try-the-templates-command)
 - [Available templates](#available-templates)
     - [Base](#base)
         - [Try it](#try-the-base-template)
-        - [FAQ](#base-faq)
-            - [What's with the directory structure?](#whats-with-the-directory-structure)
-            - [Development configuration?](#base-what-do-i-need-to-configure-for-development)
-            - [Production configuration?](#base-what-do-i-need-to-configure-for-production)
     - [Auth](#auth)
         - [Try it](#try-the-auth-template)
-        - [FAQ](#auth-faq)
-            - [Development configuration?](#auth-what-do-i-need-to-configure-for-development)
-            - [Production configuration?](#auth-what-do-i-need-to-configure-for-production)
     - [Custom](#custom)
         - [Try it](#try-the-custom-template)
         - [FAQ](#custom-faq)
             - [Any guides on how to make custom templates?](#any-guides-on-how-to-make-custom-templates)
+- [The .oratsrc file](#the-oratsrc-file)
 - [Wiki](https://github.com/nickjj/orats/wiki)
     - [What to look at after making a new project](https://github.com/nickjj/orats/wiki/What-to-look-at-after-making-a-new-project)
-    - [Get your application on a server](https://github.com/nickjj/orats/wiki/Get-your-application-on-a-server)
 
 ## System dependencies
 
@@ -61,15 +43,13 @@ Before running orats...
 - [Postgres](https://wiki.postgresql.org/wiki/Detailed_installation_guides)
 - [Redis](http://redis.io/topics/quickstart)
 - Ruby 2.1.x - [chruby](https://github.com/postmodern/chruby) | [rbenv](https://github.com/sstephenson/rbenv) | [rvm](https://rvm.io/)
-- Rails 4.1.x - `gem install rails -v '~> 4.1.2'`
+- Rails 4.1.x - `gem install rails -v '~> 4.1.4'`
 
 #### You should install
 
-- [Ansible](http://docs.ansible.com/intro_installation.html)
-    - If you plan to use the ansible features (optional)
 - [Imagemagick](https://www.google.com/search?q=install+imagemagick)
     - If you want favicons to be automatically created (optional)
-    
+
 #### You need these processes to be running
 
 - Postgres
@@ -83,262 +63,25 @@ Or if you already have orats then run `gem update orats` to upgrade to the lates
 
 ## Commands
 
-Here is an overview of the available commands. You can find out more information about each command and flag by running  `orats help <command name>` from your terminal. You can also type `orats` on its own to see a list of all commands.
-
-- **Create a new orats project**:
-    - `orats project <TARGET_PATH> --pg-password foo`
-    - Configuration:
-        - Optionally takes: `--pg-location [localhost]`
-        - Optionally takes: `--pg-username [postgres]`
-        - Optionally takes: `--redis-location [localhost]`
-        - Optionally takes: `--redis-password []`
-    - Template:
-        - Optionally takes: `--template []`
-        - Optionally takes: `--custom []`
-    - Project:
-        - Optionally takes: `--skip-ansible [false]`
-        - Optionally takes: `--skip-server-start [false]`
-
-- **Create an ansible inventory**:
-    - `orats inventory <TARGET_PATH>`
-
-- **Create an ansible playbook**:
-    - `orats playbook <TARGET_PATH>`
-    - Template:
-        - Optionally takes: `--custom []`
-
-- **Create a new ansible role**:
-    - `orats role <TARGET_PATH>`
-    - Configuration:
-        - Optionally takes: `--repo-name []`
-    - Template:
-        - Optionally takes: `--custom []`
-
-- **Delete a directory and optionally all data associated to it**:
-    - `orats nuke <TARGET_PATH>`
-    - Optionally takes: `--skip-data [false]`
-
-- **Compare differences between your orats files and the latest version's 
-files**:
-    - `orats diff [options]`
-    - Optionally takes: `--galaxyfile []`
-    - Optionally takes: `--playbook []`
-    - Optionally takes: `--hosts []`
-    - Optionally takes: `--inventory []`
-
-- **Get a list of available orats templates**:
-    - `orats templates`
-
-### Project
-
-The project command kicks off a new orats project. It will always use the 
-base template and optionally allows you to provide the `--template foo` flag 
-where `foo` would be an available template provided by orats.
-
-You can also supply your own custom template which is explained in the 
-[custom template](#custom) section.
-
-Get started by checking out what the [base template](#base) provides.
-
-### Inventory
-
-The project command automatically creates an inventory for you but it also 
-has an optional flag to skip doing it by providing `--skip-ansible`.
-
-In case you decided to `--skip-ansible` or decided to delete your inventory 
-from a really old project to let orats generate a new one for you then you can
- generate a new inventory on its own.
-
-You may also consider using this command if you happen to use ansible but are
- not interested in the orats project because here is what it does:
-
-#### Features
-
-- Create an `inventory` folder
-    - Create a `hosts` files
-        - Populate it with a few groups used by an orats project
-    - Create a `group_vars/all.yml` file
-        - Populate it with a bunch of configuration for an orats project
-- Create a `secrets` folder
-    - Generate strong passwords for:
-        - Your postgres user
-        - Your redis server
-        - Your mail account
-    - Generate tokens for:
-        - Rails
-        - Devise
-        - Devise pepper
-    - Create a single private/public ssh keypair
-        - This could be used to send to your servers
-    - Create self signed ssl certificates to test/support ssl
-    - Create a monit pem file for its optional http interface over ssl
-
-#### Try the inventory command
-
-`orats inventory myinventory`
-
-### Playbook
-
-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 playbook template creates an ansible playbook that will provision a **ubuntu 12.04 LTS server**. It can be hosted anywhere as there are no hard requirements on any specific host.
-
-#### Server breakdown
-
-Everything is broken up into ansible roles so you can quickly scale out horizontally or by splitting up your server groups such that your database is on a separate server than your application.
-
-- **Security**:
-    - Logging into the server is only possible with an ssh key
-    - Root login is disable
-    - fail2ban is setup and configurable
-    - ferm (firewall) is setup to block any ports not exposed by you
-    - All stack specific processes are running with less privileges than root
-- **User**:
-    - A single deploy user is created
-- **Services and runtimes**:
-    - Postgres
-    - Redis
-    - NodeJS
-    - Ruby
-- **Process management**:
-    - Your rails app and sidekiq have `init.d` scripts
-    - Your rails app and sidekiq are monitored using `monit`
-
-#### Try the playbook command
-
-`orats playbook myplaybook`
-
-#### Ansible roles used
-
-- `nickjj.locale` https://github.com/nickjj/ansible-locale [![Build Status](https://secure.travis-ci.org/nickjj/ansible-locale.png)](http://travis-ci.org/nickjj/ansible-locale)
-- `nickjj.sshd` https://github.com/nickjj/ansible-sshd [![Build Status](https://secure.travis-ci.org/nickjj/ansible-sshd.png)](http://travis-ci.org/nickjj/ansible-sshd)
-- `nickjj.ferm` https://github.com/nickjj/ansible-ferm [![Build Status](https://secure.travis-ci.org/nickjj/ansible-ferm.png)](http://travis-ci.org/nickjj/ansible-ferm)
-- `nickjj.fail2ban` https://github.com/nickjj/ansible-fail2ban [![Build Status](https://secure.travis-ci.org/nickjj/ansible-fail2ban.png)](http://travis-ci.org/nickjj/ansible-fail2ban)
-- `nickjj.user` https://github.com/nickjj/ansible-user [![Build Status](https://secure.travis-ci.org/nickjj/ansible-user.png)](http://travis-ci.org/nickjj/ansible-user)
-- `nickjj.postgres` https://github.com/nickjj/ansible-postgres [![Build Status](https://secure.travis-ci.org/nickjj/ansible-postgres.png)](http://travis-ci.org/nickjj/ansible-postgres)
-- `nickjj.ruby` https://github.com/nickjj/ansible-ruby [![Build Status](https://secure.travis-ci.org/nickjj/ansible-ruby.png)](http://travis-ci.org/nickjj/ansible-ruby)
-- `nickjj.rails` https://github.com/nickjj/ansible-rails [![Build Status](https://secure.travis-ci.org/nickjj/ansible-rails.png)](http://travis-ci.org/nickjj/ansible-rails)
-- `nickjj.whenever` https://github.com/nickjj/ansible-whenever [![Build Status](https://secure.travis-ci.org/nickjj/ansible-whenever.png)](http://travis-ci.org/nickjj/ansible-whenever)
-- `nickjj.pumacorn` https://github.com/nickjj/ansible-pumacorn [![Build Status](https://secure.travis-ci.org/nickjj/ansible-pumacorn.png)](http://travis-ci.org/nickjj/ansible-pumacorn)
-- `nickjj.sidekiq` https://github.com/nickjj/ansible-sidekiq [![Build Status](https://secure.travis-ci.org/nickjj/ansible-sidekiq.png)](http://travis-ci.org/nickjj/ansible-sidekiq)
-- `nickjj.monit` https://github.com/nickjj/ansible-monit [![Build Status](https://secure.travis-ci.org/nickjj/ansible-monit.png)](http://travis-ci.org/nickjj/ansible-monit)
-- `nickjj.nodejs` https://github.com/nickjj/ansible-nodejs [![Build Status](https://secure.travis-ci.org/nickjj/ansible-nodejs.png)](http://travis-ci.org/nickjj/ansible-nodejs)
-- `nickjj.nginx` https://github.com/nickjj/ansible-nginx [![Build Status](https://secure.travis-ci.org/nickjj/ansible-nginx.png)](http://travis-ci.org/nickjj/ansible-nginx)
-- `DavidWittman.redis` https://github.com/DavidWittman/ansible-redis [![Build Status](https://secure.travis-ci.org/DavidWittman/ansible-redis.png)](http://travis-ci.org/DavidWittman/ansible-redis)
-
-#### Playbook FAQ
-
-##### What is the Galaxyfile?
-
-It is similar to what a Gemfile is for ruby.
+To get the details of each command then please run `orats help` from the terminal. Below is a high level overview of what the main commands do.
 
-When you generate a playbook it will create a `roles` folder inside of the 
-target path you specified. The roles folder will contain all of the above 
-roles.
+### New
 
-When you run the playbook it will use these files when it provisions
- your server(s).
- 
-This allows you to easily update the versions of each ansible role without 
-having to download a new version of orats.
-
-##### How do I update the roles for an existing playbook?
-
-Just run `orats playbook myplaybook` and it will overwrite 
-the roles in `myplaybook/roles` using the versions supplied in your 
-`Galaxyfile`. This is useful to run when a role requires a bug fix or new features were added.
-
-Since the roles are self contained in the playbook this allows you to have 
-multiple playbooks with certain role versions in case you have older orats 
-projects which require older role versions.
-
-### Role
-
-The role command generates an ansible role with a few opinions. The 
-`ansible-galaxy` command that ships with ansible already comes with an `init`
- function but the formatting of the files wasn't to my liking.
- 
-I also wanted it to add in tests using travis-ci and setup a basic 
-idempotence test for all new roles.
-
-#### Changes vs ansible-galaxy init
-
-All of the changes have git commits to go with them. After generating a role you
- can type `git reflog` to get a list of changes.
+The new command kicks off a new orats app. It will always use the base template and optionally allows you to provide the `--template foo` flag where `foo` would be an available template provided by orats.
 
-- **Core changes**:
-    - Add travis-ci tests
-    - Remove the `vars` folder
-    - Add `LICENSE` (MIT)
-    - Add `.gitignore`
-- **meta/main.yml**:
-    - Automatically fill in the author name based on your git name
-- **README.md**:
-    - Add a travis badge
-    - Add a section to link back to your role on the official ansible galaxy
-    - Automatically fill in your repo name, role name and name where necessary
-    - Add instructions for using the role in an example playbook
-    - Add a todo list for you to make the role your own
-
-#### Try the role command
-
-##### Basic
-
-`orats role your_github_user_name.myrole`
-
-##### Custom repo name
-
-`orats role your_github_user_name.mynewrole --repo-name ansible-mynewrole`
-
-The custom repo name is probably what you'll want to use all the time if you 
-plan to make your roles open source. For example my roles are named things like `nickjj.postgres` and `nickjj.rails`. However my repos are named `ansible-postgres` and `ansible-rails`.
-
-When you submit your role to the galaxy you would use `rails` as the 
-optional name for your role.
-
-### Diff
-
-The goal of the diff command is to compare your orats generated files with 
-the latest version to see what differences there are between the 2.
-
-You can compare nothing in which case it just gives you back your version of 
-the orats gem vs the latest gem version or you can add paths to 1 or all of the 
-files below.
+You can also supply your own custom template which is explained in the [custom template](#custom) section.
 
-##### Galaxyfile
-
-When you supply the `--galaxyfile` flag along with a path to your `Galaxyfile` 
-it will show you a list of missing, outdated and extra roles with the versions.
-
-##### Playbook
-
-When you supply the `--playbook` flag along with a path to your 
-`site.yml` file it will show you a list of missing or extra roles.
-
-##### Hosts
-
-When you supply the `--hosts` flag along with a path to your `hosts` file it 
-will show you a list of missing or extra groups.
-
-##### Inventory
-
-When you supply the `--inventory` flag along with a path to your 
-`group_vars/all.yml` file it will show you a list of missing or extra variables.
-
-#### Wait, there is an easier way to compare everything
-
-If you kept the default file names for the files orats generated then you can pass in the path to your inventory directory and playbook directory and it will compare everything for you.
+Get started by checking out what the [base template](#base) provides.
 
-#### Try the diff command
+### Nuke
 
-##### Individual files
+You can delete an app using the nuke command. It is much better than just using `rm -rf` because it will clean up the postgres and redis namespace as long as you don't disable that functionality with the `--skip-data` flag.
 
-`orats diff -g /path/to/playbook/Galaxyfile -p /path/to/playbook/site.yml -h 
-/path/to/project/inventory/hosts -i /path/to/project/inventory/group_vars/all.yml`
+#### Try the nuke command
 
-##### Shortcut
+You will need to have generated an app before trying this. Check out the [try the base template](#try-the-base-template) section to learn how to generate an app.
 
-`orats diff -i /path/to/my/project/inventory -p /path/to/playbook`
+`orats nuke /tmp/someapp --pg-password foo`
 
 ### Templates
 
@@ -407,7 +150,7 @@ All of the changes have git commits to go with them. After generating a project
 
 #### Try the base template
 
-`orats project myapp --pg-password foo`
+`orats new myapp --pg-password foo`
 
 #### Base FAQ
 
@@ -421,54 +164,6 @@ In order to do this it must know your postgres location, username and password.
 
 If your redis server is configured to use a password then you must also pass in `--redis-password foo`.
 
-##### What's with the directory structure?
-
-Let's say you were to generate a new project at *~/tmp/myapp*, then you would get the following paths:
-
-```
-~/tmp/myapp/inventory
-~/tmp/myapp/secrets
-~/tmp/myapp/services
-```
-
-The **inventory** path contains the ansible inventory files for this project. This would be where your host addresses go along with configuration settings for this project.
-
-The **secrets** path contains the passwords for various things as well as ssh keypairs and ssl certificates. This path should be kept out of version control. You could also go 1 extra step and encrypt this directory locally.
-
-The **services** path contains your rails application. I like to call it services because you might have multiple services in 1 project.
-
-If you run the command with `--skip-ansible` you will not get the inventory and services.
-
-<a name="base-what-do-i-need-to-configure-for-development"></a>
-##### What do I need to configure for development?
-
-Pretty much everything is contained within environment variables. They are stored in the `.env` file located in the root directory of the rails application. It should be self explanatory. This file is also added to `.gitignore`.
-
-<a name="base-what-do-i-need-to-configure-for-production"></a>
-##### What do I need to configure for production?
-
-If you are using ansible then you should open `inventory/group_vars/all.yml` and take a peek. Everything there has comments. Assuming you have everything hosted on 1 server then at minimum you will only need to change `rails_deploy_git_url` to get going.
-
-The above variable is the repo where your code is contained. Ansible will clone that repo in an idempotent way.
-
-You will also need to put the correct server IP(s) in `inventory/hosts`. At this point that's all you need to change to successfully provision a server. 
-
-There are many other variables that you would likely change too such as adding your google analytics UA, S3 keys and all of the mail settings.
-
-You may also want to tinker with the following values for performance reasons based on your server(s).
-
-```
-  DATABASE_POOL: 25
-
-  PUMA_THREADS_MIN: 0
-  PUMA_THREADS_MAX: 16
-
-  # ensure there are always at least 2 workers so puma can properly do phased restarts
-  PUMA_WORKERS: "{{ ansible_processor_cores if ansible_processor_cores > 1 else 2 }}"
-
-  SIDEKIQ_CONCURRENCY: 25
-```
-
 ### Auth
 
 This is the auth template which gets merged into the base template. It contains a basic authentication setup using devise and pundit.
@@ -515,28 +210,11 @@ All of the changes have git commits to go with them. After generating a project
 
 #### Try the auth template
 
-`orats project myauthapp --template auth --pg-password foo`
-
-#### Auth FAQ
-
-##### What do those flags do?
-
-You should read the [try the base template](#try-the-base-template) section to get an idea of what they do.
-
-<a name="auth-what-do-i-need-to-configure-for-development"></a>
-##### What do I need to configure for development?
-
-You may want to change `ACTION_MAILER_DEVISE_DEFAULT_FROM` in `.env`.
-
-<a name="auth-what-do-i-need-to-configure-for-production"></a>
-##### What do I need to configure for production?
-
-You will want to change `ACTION_MAILER_DEVISE_DEFAULT_FROM` in `inventory/group_vars/all.yml`.
+`orats new myauthapp --template auth --pg-password foo`
 
 ### Custom
 
-You can pass custom templates into both the `project` and `playbook` commands
-. It works exactly like passing a custom application template to `rails new`.
+You can pass custom templates into the `new` command. It works exactly like passing a custom application template to `rails new`.
 
 Pass in a custom template by providing the `--custom` flag along with either a local path or a URL.
 
@@ -553,7 +231,7 @@ S
 
 #### Try the custom template
 
-`orats project /tmp/customexample -p foo --custom /tmp/foo.rb`
+`orats new /tmp/customexample -p foo --custom /tmp/foo.rb`
 
 #### Custom FAQ
 
@@ -563,5 +241,32 @@ S
 There's the official [rails guide on custom application templates]
 (http://guides.rubyonrails.org/rails_application_templates.html).
 
-You can also view the [orats project templates](https://github.com/nickjj/orats/tree/master/lib/orats/templates) to use as inspiration. All of 
-the template files are self contained.
+You can also view the [orats templates](https://github.com/nickjj/orats/tree/master/lib/orats/templates) to use as inspiration. All of the template files are self contained.
+
+## The .oratsrc file
+
+Both the `new` and `nuke` commands are dependent on having your postgres and redis login information because they need to connection to those databases to perform various tasks.
+
+There are 5 flags to configure for this:
+
+- `--pg-location` (defaults to localhost)
+- `--pg-username` (defaults to postgres)
+- `--pg-password` (defaults to an empty string)
+- `--redis-location` (defaults to localhost)
+- `--redis-password` (defaults to an empty string)
+
+For most people you will only need to supply the postgres password but still it's annoying to have to type those flags in every time you create a new app or nuke an app. It's really annoying if you develop inside of linux containers like myself which means the location is not localhost.
+
+This is where the `.oratsrc` file comes into play. By default it will look for one in your home directory but you can pass in a location directly with the `--rc` flag.
+
+This file can contain the above flags. You might have one created at `~/.oratsrc`
+ and it could look like this:
+
+```
+--pg-location 192.168.144.101
+--pg-username nick
+--pg-password pleasedonthackme
+--redis-location 192.168.144.101
+```
+
+You can supply as many or little flags as you want.

data/Rakefile

@@ -1 +1 @@
-require 'bundler/gem_tasks'
+require 'bundler/gem_tasks'

data/bin/orats

@@ -10,8 +10,11 @@
 git_path = File.expand_path('../../.git', __FILE__)
 
 if File.exist?(git_path)
-  $:.unshift(File.expand_path('../../lib', __FILE__))
+  $LOAD_PATH.unshift(File.expand_path('../../lib', __FILE__))
 end
 
 require 'orats/cli'
-Orats::CLI.start(ARGV)
+require 'orats/argv_adjust'
+
+argv = Orats::ARGVAdjust.new.init
+Orats::CLI.start(argv)

data/lib/orats/argv_adjust.rb

@@ -0,0 +1,61 @@
+require 'orats/ui'
+
+module Orats
+  # adjust ARGV by adding args from the .oratsrc file if necessary
+  class ARGVAdjust
+    include Orats::UI
+
+    def initialize(argv = ARGV)
+      @argv = argv
+
+      @default_rc_file = File.expand_path('~/.oratsrc')
+      @rc_path = ''
+    end
+
+    def init
+      rc_path @argv.first
+      return @argv if @rc_path.empty?
+
+      argv
+    end
+
+    private
+
+    def rc_path(command)
+      return unless command == 'new' || command == 'nuke'
+
+      rc_flag = @argv.index { |item| item.include?('--rc') }
+
+      if rc_flag
+        cli_rc_file(rc_flag)
+      elsif File.exist?(@default_rc_file)
+        @rc_path = @default_rc_file
+      end
+    end
+
+    def argv
+      if File.exist?(@rc_path)
+        extra_args = File.readlines(@rc_path).flat_map(&:split)
+        results 'Using values from an .oratsrc file',
+                'args', extra_args.join(' ')
+        puts
+
+        (@argv += extra_args).flatten
+      else
+        error 'The .oratsrc file cannot be found', @rc_path
+      end
+    end
+
+    def cli_rc_file(index)
+      rc_value = @argv[index]
+
+      if rc_value.include?('=')
+        @rc_path = rc_value.gsub('--rc=', '')
+        @argv.slice! index
+      elsif rc_value == '--rc'
+        @rc_path = @argv[index + 1]
+        @argv.slice! index + 1
+      end
+    end
+  end
+end