Manually specify ruby_buildpack in cf staging manifest as well

vmware-archive · May 3, 2016 · cf9530e · cf9530e
1 parent 3b8d014
commit cf9530e
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/config/cf/manifest-staging.yml b/config/cf/manifest-staging.yml
@@ -5,6 +5,7 @@ applications:
   instances: 1
   host: project-monitor-staging
   path: ../../
+  buildpack: ruby_buildpack
   command: bundle exec rake db:migrate && bundle exec rake db:seed && bundle exec unicorn -p $PORT -c ./config/unicorn.rb
   services:
   - db-staging
@@ -13,6 +14,7 @@ applications:
   memory: 512M
   instances: 1
   path: ../../
+  buildpack: ruby_buildpack
   command: bundle exec rake jobs:work
   no-route: true
   services:
@@ -22,6 +24,7 @@ applications:
   memory: 512M
   instances: 1
   path: ../../
+  buildpack: ruby_buildpack
   command: bundle exec clockwork ./clockwork.rb
   no-route: true
   services:
@@ -31,6 +34,7 @@ applications:
   memory: 1024M
   instances: 1
   path: ../../
+  buildpack: ruby_buildpack
   command: bundle exec rake projectmonitor:poller
   no-route: true
   services: