just a detial more... for get the gems in the gemfile you must execute "bundle install" This way a third person don't have to know what gems are needed for you application, only execute bundle intall and ready
On 2 ago, 11:02, Peter Hickman <[email protected]> wrote: > On 2 August 2011 09:44, 7stud -- <[email protected]> wrote: > > > In your example, one gem is included in development mode(and presumably > > production mode), and another gem is included for testing mode only. So > > Only if there is a > > group :production do > gem 'xyz' > end > > or the line > > gem 'xyz' > > not included in a 'group ... do' block. Otherwise presume nothing. > > For further clarity Rails has three modes by *convention only* and you > can create as many as you like. We have 'staging' for our staging > environment and 'fallback' for the servers that will come online when > if the hosting of the main servers fails. You could also have a > 'q_and_a' environment for the QA team to do it's testing on. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
