Note that there are some explanatory texts on larger screens.

plurals
  1. POIs it a good idea to use a different gemset for staging and production environments?
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COTypically your staging is going to be running on a different server than your production, so I am not sure if you get much benefit from using a different gemset? Also I am pretty sure 'bundler/capistrano' will install all of the gems to shared/bundle under the install directory, your install directories would need to be different if running staging and production on the same machine, so I think you get gem isolation by default?
      singulars
    2. COTrue, separate servers might actually make this part a bit easier for me, but this app's use of staging is so lightweight that I can run both apps on the same server. You're right about the `shared/bundle` directory, too. I hadn't noticed that. I wonder what the 'GEM_PATH' environment variable is, then. I ran a script that just does `puts ENV['GEM_PATH']`, and it reported `/usr/local/rvm/gems/ree-1.8.7-2012.02@appname-staging:/usr/local/rvm/gems/ree-1.8.7-2012.02@global`. Maybe bundler alone uses `GEM_PATH`, but 'bundler/capistrano' uses the `shared/bundle` directory (?).
      singulars
    3. COi am assuming you have different Gemfiles between production and staging right now? `cd staging_dir; bundle list` and `cd production_dir; bundle list` - now just make sure everything you do uses `bundle exec` when running from either staging or production, rake tasks, boot your server (passenger, unicorn, thin etc...)
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload