Hi, The thor merb:dependencies:install task should bundle the actual application dependencies indeed, including extlib.
However, it doesn't bundle all secondary dependencies unless you specify --include-dependencies Bundling a webserver is certainly possible, but I don't see an immediate need for that. If you need to: thor merb:gem:install thin --binaries But be sure to run thor merb:dependencies:redeploy if you're going to deploy on another platform. Cheers, Fabien On Oct 23, 6:52 pm, "Paul Carey" <[EMAIL PROTECTED]> wrote: > Hi > > I'm running RC2 and deployed onto a clean system today. > > I had understood the point of bundling was to ensure that conflicts > don't arise after deploying to remote machines where gem versions > might differ from those on the local dev machine . So, I'd have > expected > thor merb:dependencies:install > to bundle all required gems into my app. But it only bundles those > dependencies listed in config/dependencies.rb plus a couple of others > (thor and rake for me). > > So when I do deploy and run merb I still have to install extlib, > erubis, json and others on the box that I'm deploying to. But if > they're already installed then I could easily suffer from a version > conflict. I have the feeling I'm missing something... > > I also wonder if its considered appropriate to bundle a webserver > (e.g. thin) with a merb app? > > Thanks > Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
