On 5/11/2013 9:02 PM, TomPave wrote:
I noticed that Capistrano doesn't use the default directory for the user
who executes the rack app server: ~/.rvm/....
Rather, it installs the gems in the vendor folder of each release. for
example:
/var/www/wonderingmachine/releases/20130512001352/vendor/bundle/ruby/2.0.0/gems/unicorn-4.6.2
This is not unique to Capistrano, but bundler-recommended setup for any
deployment install, with OR without Capistrano. It's one of the effects
of using "bundle --deployment", which is what bundler recommends in
deployment copies of an app.
I would recommend asking questions in a Bundler-related venue about why
bundler makes this decision/recommendation about deployment -- before
deciding to make a different decision yourself, understanding the
intention.
If you do want to make a different decision, it can quite possibly be
done simply with different or additional bundler arguments than
"--deployment" -- you probably don't need to do a lot of hacking, just
write a capistrano task that executes bundler with different arguments
that the bundler-recommended "--deployment".
But it probably doesn't make sense for Capistrano to ship with a task
that does anything other than what bundler recommends for deployment. If
you think what bundler recommends for deployment is incorrect, best take
that up with bundler.
Jonathan
--
--
* You received this message because you are subscribed to the Google Groups
"Capistrano" group.
* To post to this group, send email to capistrano@googlegroups.com
* To unsubscribe from this group, send email to
capistrano+unsubscr...@googlegroups.com For more options, visit this group at
http://groups.google.com/group/capistrano?hl=en
---
You received this message because you are subscribed to the Google Groups "Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to capistrano+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
