suspenders 1.1.1 → 1.1.2

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    suspenders (1.0.1)
+    suspenders (1.1.1)
       bundler (>= 1.1)
       hub (~> 1.10.2)
       rails (= 3.2.6)

data/NEWS.md

@@ -1,3 +1,8 @@
+1.1.2 (August 6, 2012)
+
+* Fix broken rake.
+* Use Heroku-compliant asset pipeline settings.
+
 1.1.1 (August 3, 2012)
 
 * Fix broken newline interpolation

data/README.md

@@ -15,7 +15,7 @@ Then run:
 
     suspenders projectname
 
-This will create a Rails 3.1 app in `projectname`. This script creates a new
+This will create a Rails 3.2 app in `projectname`. This script creates a new
 new git repository. It is not meant to be used against an existing repo.
 
 Gemfile
@@ -50,6 +50,7 @@ Suspenders also comes with:
 
 * Rails' flashes set up and in application layout.
 * A few nice time formats.
+* [Heroku-compliant asset pipeline settings](https://devcenter.heroku.com/articles/rails3x-asset-pipeline-cedar/).
 
 Heroku
 ------

data/lib/suspenders/app_builder.rb

@@ -27,6 +27,12 @@ module Suspenders
       run 'cp config/environments/production.rb config/environments/staging.rb'
     end
 
+    def initialize_on_precompile
+      inject_into_file 'config/application.rb',
+        "\n    config.assets.initialize_on_precompile = false",
+        :after => 'config.assets.enabled = true'
+    end
+
     def create_partials_directory
       empty_directory 'app/views/application'
     end
@@ -167,12 +173,6 @@ module Suspenders
       run "#{path_addition} heroku create #{app_name}-staging    --remote=staging"
     end
 
-    def document_heroku
-      heroku_readme_path = find_in_source_paths 'HEROKU_README.md'
-      documentation = File.open(heroku_readme_path).read
-      inject_into_file('README.md', "#{documentation}\n", :before => 'Most importantly')
-    end
-
     def create_github_repo(repo_name)
       path_addition = override_path_for_tests
       run "#{path_addition} hub create #{repo_name}"

data/lib/suspenders/generators/app_generator.rb

@@ -61,6 +61,7 @@ module Suspenders
     def setup_staging_environment
       say 'Setting up the staging environment'
       build :setup_staging_environment
+      build :initialize_on_precompile
     end
 
     def create_suspenders_views
@@ -143,7 +144,6 @@ module Suspenders
       if options[:heroku]
         say 'Creating Heroku apps'
         build :create_heroku_apps
-        build :document_heroku
       end
     end
 

data/lib/suspenders/version.rb

@@ -1,3 +1,3 @@
 module Suspenders
-  VERSION = '1.1.1'
+  VERSION = '1.1.2'
 end

data/templates/Gemfile_additions

@@ -18,7 +18,7 @@ group :development, :test do
 end
 
 group :test do
-  gem 'cucumber-rails', '1.3.0'
+  gem 'cucumber-rails', '1.3.0', :require => false
   gem 'factory_girl_rails'
   gem 'bourne'
   gem 'database_cleaner'

data/templates/README.md.erb

@@ -173,6 +173,10 @@ Watch logs and metrics dashboards. If the feature is working, merge into master.
     git merge production --ff-only
     git push origin master
 
+Use scripts from [thoughtbot/dotfiles](http://github.com/thoughtbot/dotfiles)
+to quickly access the Heroku console, backup the production database, and
+transfer production data to staging.
+
 Formatting
 ----------
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: suspenders
 version: !ruby/object:Gem::Version
-  version: 1.1.1
+  version: 1.1.2
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-08-03 00:00:00.000000000 Z
+date: 2012-08-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -132,7 +132,6 @@ files:
 - suspenders.gemspec
 - templates/Gemfile_additions
 - templates/Guardfile
-- templates/HEROKU_README.md
 - templates/Procfile
 - templates/README.md.erb
 - templates/_flashes.html.erb

data/templates/HEROKU_README.md

@@ -1,66 +0,0 @@
-Staging and production environments
------------------------------------
-
-We're using Heroku as a hosting provider. Deploying to Heroku is done via git. So, set up your git remotes for each environment:
-
-    git remote add staging git@heroku.com:your-app-staging.git
-    git remote add production git@heroku.com:your-app-production.git
-
-Heroku
-------
-
-The following are mostly aliases from the `dotfiles` script.
-
-To access your code on Heroku:
-
-    staging
-    production
-
-That will drop you into a Rails console for either environment. You can run ActiveRecord queries from there.
-
-To dump staging or production data into your development environment:
-
-    db-pull-staging
-    db-pull-production
-
-You will see progress bars for each db index and table.
-
-We can create a database backup at any time:
-
-    db-backup-production
-
-View backups:
-
-    db-backups
-
-To destroy a backup:
-
-    heroku pgbackups:destroy b003 --remote production
-
-Transfer production data to staging:
-
-    db-copy-production-to-staging
-
-More information in the [Dev Center](http://devcenter.heroku.com/articles/pgbackups).
-
-To check the status of running app servers, background jobs, cron jobs, etc:
-
-    staging-process
-    production-process
-
-To see the performance of the staging application, see:
-
-    https://heroku.newrelic.com/...
-
-To see the performance of the production application, see:
-
-    https://heroku.newrelic.com/...
-
-ENV variables
--------------
-
-ENV variables like AWS keys should not be in the source code. They are configuration and should be stored as ENV variables. On Heroku, they are called "config variables." You can pull config variables using the `heroku-config` plugin that comes with the `laptop` script:
-
-    heroku config:pull --remote staging
-
-You'll see the Amazon credentials as config vars. You should delete lines that don't apply, like Redis to Go connection strings.