Few days ago, I posted an article covering this use case: http://merbist.com/2008/09/23/deploying-a-bundled-merb-app-merb-097/ I'll update the wiki to reflect the steps.
Few extra points: - Please do not add your src folder to your git repo, you don't need that. - Only native gems get rebuilt - Because of "set :deploy_via, :remote_cache" your bundled gems don't get pushed every time. - "I moved from Rails to merb to get away from complexity." Merb is more complicated than Rails but it's also more flexible and more powerful, because Merb is gem based, things are more complicated but we are trying to make them easier. -Matt On Thu, Oct 2, 2008 at 7:34 AM, Julian Leviston <[EMAIL PROTECTED]> wrote: > convincingly confusing :-) j > > On 03/10/2008, at 12:25 AM, Yehuda Katz wrote: > > And by convincing, I of course meant confusing :P > > On Thu, Oct 2, 2008 at 10:25 AM, Yehuda Katz <[EMAIL PROTECTED]> wrote: > >> Apologies for it seeming convincing. Regarding your central problem: >> # some gems feature compiled C extensions - these need to be recompiled on >> your >> # target deployment platform (use Capistrano, God...) >> thor merb:gems:redeploy >> >> That will recompile any C extensions on your target platform. >> >> -- Yehuda >> >> >> On Thu, Oct 2, 2008 at 5:50 AM, Jon Hancock <[EMAIL PROTECTED]>wrote: >> >>> >>> I am attempting to work with merb edge. In the past this seemed a >>> simple thing but now I am educating myself on the use of thor as the >>> new new way to work with edge and package it inside my project. I >>> have a few questions and concerns. >>> >>> Synch-ing from dev to test or production pushes lots of stuff. How >>> are platform specific compiles handled when I re-checkout on my >>> production server? >>> So I follow the instructions from here >>> >>> http://wiki.merbivore.com/pages/getting-merb-and-datamapper-edge-step-by-step >>> and/or<http://wiki.merbivore.com/pages/getting-merb-and-datamapper-edge-step-by-stepand/or> >>> here >>> http://merbunity.com/tutorials/18 >>> This pulls git repos into my local app structure and packages gems. >>> I'm doing this under OS X. I deploy on linux. Some of this code has >>> C that needs to be recompiled (meaning gems repackaged?) for the >>> target machine. How does this happen? I assume I am supposed to push >>> from my OS X git repo to my production machine. But don't i need to >>> rebuild those platform specific object files? >>> >>> All I want is two things: >>> 1 - be able to develop on edge or some other version from git. >>> 2 - be able to deploy what I"ve tested with >>> >>> At the moment, this thor thing seems overkill and isn't working for >>> me. I moved from Rails to merb to get away from complexity. >>> >>> Any help please? >>> >>> thanks, Jon >>> http://shellshadow.com >>> >>> >>> >>> >>> >>> >>> >>> >> >> >> -- >> Yehuda Katz >> Developer | Engine Yard >> (ph) 718.877.1325 >> > > > > -- > Yehuda Katz > Developer | Engine Yard > (ph) 718.877.1325 > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
