engineyard-local 0.2.1 → 1.0.1

data/Gemfile

@@ -6,6 +6,7 @@ group :test do
   gem "rake"
   gem "shoulda-context"
   gem "mocha"
+  gem "rails" #required for integration tests to generate test project
 end
 
 # TODO assumes 1.9 for devs :(

data/Gemfile.lock

@@ -1,14 +1,43 @@
 PATH
   remote: .
   specs:
-    engineyard-local (0.1.0)
+    engineyard-local (0.2.1)
       thor (~> 0.14.6)
       vagrant (= 1.0.1)
 
 GEM
   remote: http://rubygems.org/
   specs:
+    actionmailer (3.2.3)
+      actionpack (= 3.2.3)
+      mail (~> 2.4.4)
+    actionpack (3.2.3)
+      activemodel (= 3.2.3)
+      activesupport (= 3.2.3)
+      builder (~> 3.0.0)
+      erubis (~> 2.7.0)
+      journey (~> 1.0.1)
+      rack (~> 1.4.0)
+      rack-cache (~> 1.2)
+      rack-test (~> 0.6.1)
+      sprockets (~> 2.1.2)
+    activemodel (3.2.3)
+      activesupport (= 3.2.3)
+      builder (~> 3.0.0)
+    activerecord (3.2.3)
+      activemodel (= 3.2.3)
+      activesupport (= 3.2.3)
+      arel (~> 3.0.2)
+      tzinfo (~> 0.3.29)
+    activeresource (3.2.3)
+      activemodel (= 3.2.3)
+      activesupport (= 3.2.3)
+    activesupport (3.2.3)
+      i18n (~> 0.6)
+      multi_json (~> 1.0)
     archive-tar-minitar (0.5.2)
+    arel (3.0.2)
+    builder (3.0.0)
     childprocess (0.3.1)
       ffi (~> 1.0.6)
     columnize (0.3.6)
@@ -16,18 +45,51 @@ GEM
     ffi (1.0.11)
     fpm (0.3.11)
       json
+    hike (1.2.1)
     i18n (0.6.0)
+    journey (1.0.3)
     json (1.5.4)
     linecache19 (0.5.12)
       ruby_core_source (>= 0.1.4)
     log4r (1.1.10)
+    mail (2.4.4)
+      i18n (>= 0.4.0)
+      mime-types (~> 1.16)
+      treetop (~> 1.4.8)
     metaclass (0.0.1)
+    mime-types (1.18)
     mocha (0.10.5)
       metaclass (~> 0.0.1)
+    multi_json (1.2.0)
     net-scp (1.0.4)
       net-ssh (>= 1.99.1)
     net-ssh (2.2.2)
+    polyglot (0.3.3)
+    rack (1.4.1)
+    rack-cache (1.2)
+      rack (>= 0.4)
+    rack-ssl (1.3.2)
+      rack
+    rack-test (0.6.1)
+      rack (>= 1.0)
+    rails (3.2.3)
+      actionmailer (= 3.2.3)
+      actionpack (= 3.2.3)
+      activerecord (= 3.2.3)
+      activeresource (= 3.2.3)
+      activesupport (= 3.2.3)
+      bundler (~> 1.0)
+      railties (= 3.2.3)
+    railties (3.2.3)
+      actionpack (= 3.2.3)
+      activesupport (= 3.2.3)
+      rack-ssl (~> 1.3.2)
+      rake (>= 0.8.7)
+      rdoc (~> 3.4)
+      thor (~> 0.14.6)
     rake (0.9.2.2)
+    rdoc (3.12)
+      json (~> 1.4)
     ruby-debug-base19 (0.11.25)
       columnize (>= 0.3.1)
       linecache19 (>= 0.5.11)
@@ -39,7 +101,16 @@ GEM
     ruby_core_source (0.1.5)
       archive-tar-minitar (>= 0.5.2)
     shoulda-context (1.0.0)
+    sprockets (2.1.2)
+      hike (~> 1.2)
+      rack (~> 1.0)
+      tilt (~> 1.1, != 1.3.0)
     thor (0.14.6)
+    tilt (1.3.3)
+    treetop (1.4.10)
+      polyglot
+      polyglot (>= 0.3.1)
+    tzinfo (0.3.33)
     vagrant (1.0.1)
       archive-tar-minitar (= 0.5.2)
       childprocess (~> 0.3.1)
@@ -57,6 +128,7 @@ DEPENDENCIES
   engineyard-local!
   fpm
   mocha
+  rails
   rake
   ruby-debug19
   shoulda-context

data/README.md

@@ -1,6 +1,8 @@
-# Engineyard Local
+# Engine Yard Local (EY Local)
 
-Engineyard Local brings the production virtual environment of Enginyard Cloud to your workstation. As a wrapper around [Vagrant](http://vagrantup.com) it uses VirtualBox, Ruby, and a custom prepackaged virtual machine image to make the creation and management of your local development environment easy, and customizations to your production environment testable.
+EY Local brings the production virtual environment of Engine Yard Cloud to your local laptop/workstation. 
+
+Engine Yard Local is a wrapper around the [Vagrant](http://vagrantup.com) tool which is written in Ruby and utilizes VirtualBox, and a custom prepackaged virtual machine image in order to make the creation and management of your local development environment easy, and customizations to your production environment testable. The project also allows you to test in an almost identical environment to Engine Yard's production cloud environment.
 
 ## Contact
 
@@ -8,18 +10,21 @@ Team members can be found on `irc.oftc.net` in `#ey-local`.
 
 ## Bugs
 
-If you have a bug please post it to the issues list, preferrable answering the following questions:
+If you encounter a bug you can post it here: [Engine Yard Local Bugs](https://support.cloud.engineyard.com/forums/20753933-engine-yard-local-bugs) *
+
+Provide the following information with the bug:
 
-1. What host platform are your running?
+1. What host platform are you running?
 2. What version of VirtualBox do you have installed? `VBoxManage -v`
 3. What version of the engineyard-local gem do you have installed? `ey-local version`
 4. What version of the vagrant gem do you have installed? `vagrant -v`
+5. Provide gist or other dump of the output that illustrates the problem.
 
-Please also provide gist or other dump of the output that illustrates the problem.
+**Note**:  If you do not have an Engine Yard customer login, you cannot log a bug on this forum. Instead, please email us: eylocal@engineyard.com OR ... better ... start a [free trial](http://www.engineyard.com) today! 
 
 ## Installation
 
-There are two primary methods of installation. If you're an OS X user you can download and run the prebuilt installer which will handle installing VirtualBox, vagrant and ey-local for you. Alternatively you can install [VirtualBox](https://www.virtualbox.org/wiki/Downloads) and [Ruby](http://www.ruby-lang.org/en/downloads/) for your platform and then perform:
+Install the latest [VirtualBox](https://www.virtualbox.org/wiki/Downloads) and [Ruby](http://www.ruby-lang.org/en/downloads/) for your platform and then perform:
 
     $ gem install engineyard-local
 
@@ -27,39 +32,41 @@ Once the install is complete you're ready to get started.
 
 ## Common Use
 
-Engineyard Local works from the root directory of your Rack based project. You can fire up a virtual environment from there with one command:
+EY Local works from the root directory of your Rack based project. You can fire up a virtual environment from there with one command:
 
-    $ cd my/app/
+    $ cd /path/to/your/application/code/
     $ ey-local up
     [ey-local] Downloading with Vagrant::Downloaders::HTTP...
 
-If you've never used ey-local before, or _did not_ use the OS X installer, it will begin the process by downloading the base virtual machine image from which all ey-local virtual environments are built. This will only happen once and ey-local will use the downloaded box for all subsequent virtual environments.
+If you've never used ey-local before, it will begin the process by downloading the base virtual machine image from which all ey-local virtual environments are built. This will only happen once and ey-local will use the downloaded box for all subsequent virtual environments.
+
+Please note that a known issue is that sometimes it will fail right after download due to not reloading configuration. If this happens to you please try another `ey-local up` immediately and the issue will likely resolve itself since the configuration will be reloaded properly this second time.
 
-After the download the virtual machine will be created and you'll be able to visit your app by pointing your browser at `33.33.33.10` which represents the virtual machine's host network location.
+After the download, the virtual machine will be created and you'll be able to visit your app by pointing your browser at the default IP address  of `33.33.33.10` which represents the virtual machine's host network location.
 
-From there you can edit your application files and see the application results as you normally would in your browser.
+From there you can edit your application files and see the application results as you normally would in your browser at the address [http://33.33.33.10/](http://33.33.33.10/)
 
 ### Stop
 
-After working on your application you might wish to suspend the virtual machine so it's not eating up cpu cycles while you're doing some thing else. Simply issue:
+After working on your application you might want to suspend the virtual machine so it's not eating up cpu cycles while you're doing some thing else. Simply issue:
 
     $ ey-local stop
 
-From the project directory to suspend the vm.
+... from your project directory to suspend the virtual machine.
 
 ### Start
 
-To restart the project after suspending it
+To restart the project's virtual machine after suspending it to continue working:
 
     $ ey-local start
 
 ### Other Commands
 
-For other sub commands including `list`, `rails`, `log`, and `exec` please use:
+For details on other possible commands including `list`, `rails`, `log`, and `exec` please see:
 
     $ ey-local help
 
-Also, ey-local is a wrapper around Vagrant itself and any commands that aren't defined for ey-local will be passed through to vagrant for execution. For example provisioning an ey-local environment is as simple as:
+Please note that the `ey-local` command is a wrapper around [Vagrant](http://vagrantup.com/) itself and any commands that aren't defined for ey-local will be passed through to Vagrant for execution. For example provisioning an ey-local environment is as simple as:
 
     $ ey-local provision
 
@@ -67,49 +74,44 @@ You can learn more about `provision` and other Vagrant commands in the [Vagrant
 
 ### Provisioning with Chef
 
-In addition to the facilities for vm provisioning provided through the Vagrantfile, ey-local also includes a sane default for chef recipes when no other provisioning mechanism is defined. To take advantage of the default simply place your recipe at `$PROJECT_ROOT/cookbooks/main/recipes/default.rb`. From there you can require other recipes.
+In addition to the facilities for VM provisioning provided through the Vagrantfile, ey-local also includes a sane default for chef recipes when no other provisioning mechanism is defined. To take advantage of the default simply place your recipe at `$PROJECT_ROOT/cookbooks/main/recipes/default.rb`. From there you can aquire other recipes.
 
-## Contributions
+## Contributing to the Engine Yard Local Project
 
 Pull requests are the preferred method for contribution to the project with a couple general guidelines:
 
 1. **Keep changesets small**. Every changed line has to be reviewed so the smaller each change is the faster the review process will be.
-2. **Keep commits small**. Keeping each child commit of a pull request small makes managing the git history easier especially for things like bisect. Additionally if the commits require a rebase by a team member resolving conflicts will be much less painful.
-3. **Discuss large changes**. If you are compelled to make some drastic change to the source please consult the team using the methods detailed earlier.
-
-### Layout
-
-The project layout uses the standard ruby gem folder structure. The best starting point for interested parties new to the source is at `lib/engineyard-local/command/group.rb`. There you'll find the Thor based command setup that is the entry point to ey-local's functionality. Thor is a holdover/stopgap before moving to the vagrant command structure, and is mostly a proxy for the command classes in the same subdirectory.
+2. **Keep commits small**. Keeping each child commit of a pull request small makes managing the git history easier especially for things like bisect. Additionally, if the commits require a rebase by a team member, resolving conflicts will be much less painful.
+3. **Discuss large changes**. If you are compelled to make some drastic change to the source, please consult the team using the methods detailed earlier.
 
-Upon viewing the individual command classes you'll likely be interested in the middleware that are used to operate on the vagrant virtual machines. The middleware is the primary abstraction that is used to keep each unit of work tiny and manageable. All of those and their helpers are to be found int the `lib/engineyard-local/middleware/` directory.
+### Engine Yard Local Project Layout
 
-### Installers
+The project layout uses the standard ruby gem folder structure. The best starting point for interested parties new to the source is at `lib/engineyard-local/command/group.rb`. There you'll find the Thor-based command setup that is the entry point to ey-local's functionality. Thor is a holdover/stopgap before moving to the Vagrant command structure, and is mostly a proxy for the command classes in the same subdirectory.
 
-There are two installation mechanisms for ey-local in the `install` subdirectory, one for a osx package and one for debs. Each has a detailed readme (`install/deb/README.md`, `install/osx/README.md`) on how to creat the packages including a full vagrant environment for the debs.
+Upon viewing the individual command classes you'll likely be interested in the middleware used to operate on the Vagrant virtual machines. The middleware is the primary abstraction that is used to keep each unit of work tiny and manageable. All of those and their helpers are to be found int the `lib/engineyard-local/middleware/` directory.
 
-### Installing HEAD
+### Installing the latest development HEAD
 
 You can install the latest from the repository with the following:
 
-    $ bundle install --path=./.bundle
-    $ bundle exec rake build
+    $ gem build engineyard-local.gemspec
     $ gem install pkg/engineyard-local-<VERSION>.gem
 
 ### Tests
 
-There are a fairly minimal set of mock/stub based unit tests
+There are a fairly minimal set of mock/stub based unit tests:
 
-    $ bundle install --path=./.bundle
-    $ bundle exec rake test
+    $ bundle install
+    $ rake test
 
-If you're developing on ruby 1.8 your bundle install should exclude the `:dev` group.
+If you're developing on Ruby 1.8 your bundle install should exclude the `:dev` group.
 
-    $ bundle install --without=dev --path=./.bundle
+    $ bundle install --without=dev
 
-If you're feeling brave you are welcome to run the integration tests as well though they will create and destroy vms over a long period of time. After the bundle install:
+If you're feeling brave you are welcome to run the integration tests as well though they will create and destroy virtual machines over a long period of time. After the bundle install:
 
-    $ bundle exec rake integration
+    $ rake integration
 
 You can also prefix that with a `DEBUG=true` to see the output from the tested commands.
 
-    $ DEBUG=true bundle exec rake integration
+    $ DEBUG=true rake integration

data/config/dna.json

@@ -1,38 +1,24 @@
 {
   "db_slaves": [
   ],
-  "nodejs": {
-    "version": "0.6.1"
-  },
-  "nginx": {
-    "version": "1.0.10-r1"
-  },
   "aws_secret_key": "",
   "ruby_version": "Ruby 1.9.3",
-  "backup_interval": 24,
-  "internal_ssh_public_key": "",
-  "admin_ssh_key": "",
   "user_ssh_key": [
-
+    ""
   ],
+  "internal_ssh_public_key": "",
+  "admin_ssh_key": "",
+  "backup_interval": 24,
   "internal_ssh_private_key": "",
+  "instance_role": "eylocal",
   "utility_instances": [
 
   ],
   "mailserver": "smtp.engineyard.com",
-  "instance_role": "eylocal",
   "crons": [
 
-  ],
-  "removed_applications": [
   ],
   "backup_window": 10,
-  "gems_to_install": [
-    {
-      "name": "bundler"
-    }
-  ],
-  "alert_email": "",
   "applications": {
     "APPNAME": {
       "auth": {
@@ -40,16 +26,16 @@
       },
       "newrelic": false,
       "https_bind_port": 443,
+      "migration_command": "rake db:migrate",
       "type": "APPTYPE",
-      "migration_command": "bundle exec rake db:migrate",
       "repository_name": "APPURL",
       "revision": "APPREVISION",
       "http_bind_port": 80,
       "run_deploy": false,
       "branch": "HEAD",
-      "deploy_key": "",
+      "run_migrations": true,
       "deploy_action": "deploy",
-      "run_migrations": false,
+      "deploy_key": "",
       "services": [
         {
           "resource": "mongrel",
@@ -67,62 +53,87 @@
         "memcached",
         "monit",
         "nginx",
-        "nginx-passenger"
+        "passenger3"
       ],
       "vhosts": [
         {
           "name": "_",
-          "role": "prod"
+          "role": "eylocal"
         }
       ]
     }
   },
-  "aws_secret_id": "",
-  "environment": {
-    "name": "prod",
-    "stack": "nginx_passenger3",
-    "framework_env": "production"
-  },
+  "gems_to_install": [
+    {
+      "name": "rails",
+      "version": "2.3.2"
+    },
+    {
+      "name": "mysql2",
+      "version": "0.3.2"
+    }
+  ],
+  "alert_email": "ALERT_EMAIL",
   "reporting_url": "",
   "users": [
     {
       "gid": "1000",
       "username": "vagrant",
       "uid": "1000",
-      "password": "abc123unme",
-      "comment": ""
+      "comment": "",
+      "password": "abc123unme"
     }
   ],
-  "db_host": "ey-local",
+  "environment": {
+    "name": "eylocal",
+    "stack": "nginx_passenger3",
+    "framework_env": "production"
+  },
+  "aws_secret_id": "",
   "packages_to_install": [
 
   ],
-  "haproxy": {
-    "username": "vagrant",
-    "password": "abc123unme"
-  },
+  "db_host": "ey-local",
   "engineyard": {
+    "this": "ey-local",
     "environment": {
       "apps": [
         {
           "name": "APPNAME",
           "newrelic": false,
-          "migration_command": "rake db:migrate",
-          "type": "APPTYPE",
           "components": [
+            {
+              "collection": [
 
+              ],
+              "key": "addons"
+            },
+            {
+              "key": "app_metadata"
+            }
           ],
           "database_name": "APPNAME",
+          "migration_command": "rake db:migrate",
+          "type": "rails",
           "repository_name": "APPURL",
-          "revision": "APPREVISION",
           "run_deploy": false,
+          "revision": "APPREVISION",
           "bundled": null,
           "branch": "HEAD",
-          "deploy_key": "",
+          "run_migrations": true,
           "deploy_action": "deploy",
-          "run_migrations": false,
+          "deploy_key": "",
           "gems": [
-
+            {
+              "name": "rails",
+              "version": "2.3.2",
+              "source": null
+            },
+            {
+              "name": "mysql2",
+              "version": "0.3.2",
+              "source": null
+            }
           ],
           "vhosts": [
             {
@@ -136,71 +147,86 @@
         }
       ],
       "ssh_keys": [
-
+        ""
       ],
+      "name": "eylocal",
       "aws_secret_key": "",
-      "name": "prod",
-      "ruby_version": null,
       "instances": [
         {
           "name": null,
           "public_hostname": "ey-local",
-          "stonith_config": {
-            "endpoint_uri": "https://cloud.engineyard.com/stonith",
-            "endpoint_token": "69576b03-5ad5-4774-acec-452fbad20a76",
-            "monitor_host": "ey-local",
-            "endpoint_id": "ey-local"
-          },
-          "role": "solo",
           "components": [
             {
               "key": "ssmtp"
             }
           ],
+          "stonith_config": {
+            "endpoint_uri": "https://cloud.engineyard.com/stonith",
+            "endpoint_token": "bbef81eb-5d48-4c6c-8282-084e2e669569",
+            "monitor_host": "ey-local",
+            "endpoint_id": "ey-local"
+          },
+          "role": "eylocal",
           "enabled": true,
           "id": "ey-local",
           "private_hostname": "ey-local",
           "reporting_url": "",
           "instance_api_config": {
             "token": "",
-            "base_url": "https://cloud.engineyard.com/instance_api",
-            "instance_id": ""
+            "instance_id": "",
+            "base_url": "https://cloud.engineyard.com/instance_api"
           },
           "awsm_token": ""
         }
       ],
       "framework_env": "production",
+      "ruby_version": null,
       "stonith_endpoint": "https://cloud.engineyard.com/stonith",
-      "backup_interval": 24,
+      "region": "us-east-1",
       "ssh_username": "vagrant",
       "internal_ssh_public_key": "",
       "admin_ssh_key": "",
-      "region": "us-east-1",
+      "backup_interval": 24,
       "internal_ssh_private_key": "",
-      "mailserver": "smtp.engineyard.com",
       "components": [
         {
           "key": "ruby_193"
         },
+        {
+          "version": "1.8.17",
+          "key": "rubygems"
+        },
+        {
+          "key": "environment_metadata"
+        },
+        {
+          "clusters": [
+
+          ],
+          "key": "metadata"
+        },
         {
           "key": "passenger3"
         }
       ],
+      "mailserver": "smtp.engineyard.com",
       "crons": [
 
       ],
       "stats_password": "abc123unme",
-      "backup_window": 10,
       "stack_name": "nginx_passenger3",
-      "ssh_password": "abc123unme",
+      "backup_window": 10,
       "backup_bucket": "",
+      "db_stack_name": "postgres9_1",
+      "ssh_password": "abc123unme",
       "alert_email": "ALERT_EMAIL",
-      "db_stack_name": "mysql",
-      "aws_secret_id": "",
       "monitoring": "monit",
-      "newrelic_key": null
-    },
-    "this": "ey-local"
+      "newrelic_key": null,
+      "aws_secret_id": ""
+    }
+  },
+  "haproxy": {
+    "username": "vagrant",
+    "password": "abc123unme"
   }
 }
-