It looks like in our effort to get certain use-cases working, we complicated some other common use-cases. We were attempting to support a fully self-contained merb application with nothing other than Ruby and Rubygems installed on the remote server. That requires the use of bin/merb (because the merb binary doesn't exist remotely).
The idea here is to make it simple to bundle Merb, but it doesn't look like we quite have it down yet. In Rails " I can throw the whole framework without hassle into vendor/rails, and it'll automatically work" works because they have rake tasks that automate it without hassle. We're trying to do the same here, but again, apparently haven't quite gotten there yet. We still have about 10 days before 1.0; we'll make this a priority. -- Yehuda On Thu, Oct 2, 2008 at 10:14 AM, Matthijs Langenberg <[EMAIL PROTECTED]>wrote: > > I feel the same Jon. Maybe it's a rubygems issue. What I like about > Rails is that I can throw the whole framework without hassle into > vendor/rails, and it'll automatically work. > No switching between 'merb' and 'bin/merb' or 'merb-freezer'. > That's why I just wait for a gem release, install it on our production > server and try to upgrade all apps at once. > > > On Thu, Oct 2, 2008 at 11: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 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 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
