I have investigated a solution with bundler capistrano radiant and rvm
for the company I am currently working with several weeks ago.
The deploy.rb file starts with this line: #require "bundler/
capistrano"
It has a simple task to install the bundle on the remote server, which
looks like this:
task :bundle do
run "cd #{release_path} && bundle install --without test"
end
And gets called before the symlink with this line: before
"deploy:symlink", :bundle
I have to start another radiant project which uses the same
infrastructure next week, so I might come across some errors which
luckily have not occurred so far. :-)
I hope this helps
Christoph
On 14 Dez., 20:17, Fima Leshinsky <[email protected]> wrote:
> hm .. if you're not using bundler then maybe i shouldnt either? maybe it's
> overkill for a noob like me who's just starting out w/ ruby / radiant. how
> do you handle the case where you want to play around w/ a gem in your dev.
> environment but not deploy it to production?
>
> On Tue, Dec 14, 2010 at 12:02 PM, Brad Herman
> <[email protected]>wrote:
>
>
>
> > I'm not entirely sure, but I would imagine you would just create a task
> > for installing the bundle in your cap file. LIke deploy:bundle:install or
> > something along those lines.
