oops! wrong link! http://wiki.merbivore.com/exp/start
On Mon, Jan 12, 2009 at 1:36 AM, Ted Han <[email protected]> wrote: > 2) You can already do both of those using either Merb or Rails. In > fact both Merb and Rails support Rack, so it doesn't matter if you > want to deploy with mongrel, or thin, or ebb, or passenger, or webrick > if you're really a masochist. > 3) The nice thing about optional components is that you have options. > 4) Datamapper is a separate project and you'd have to ask them whether > they'd want to patch that. I don't think it really matters one way or > the other. > 5) Merb-auth isn't part of the core. It is part of the default merb > stack, but it's not part of merb-core (again yay componentization). > 6) I'm workin' on one for merb right now... :P > http://wiki.merbivore.com/exp/start#helping_out If anyone is > interested in helping out there are instructions at the top. > > -T > > On Sun, Jan 11, 2009 at 7:24 PM, MilesTogoe <[email protected]> wrote: >> >> I saw the post asking us to send in what we see are important features >> to be in Rails 3.0. Here are some of my thoughts: >> >> 1) continue to have webrick (merb now seems to require mongrel and >> mongrel just seems to give us occasional problems) >> 2) for deployment - run on nginx plus passenger since I hear nginx is so >> much faster and less memory intensive than apache and passenger makes >> deployment simple >> 3) convert AR migrations and model files to datamapper - since we're not >> changing the data, just the ORM definitions and datamapper migrations >> updates and keeping definitions in the are far superior >> 4) make datamapper work with has_many - not sure what real advantage >> has_n is aside from a few less characters (maybe easy to just have >> either work) >> 5) merb auth and sessions - rails requires a 3rd party auth plugin - >> auth is too important and should be in core and work well with session >> 6) good "how-to" wiki - since there will be likely be many conversion >> questions based on different user needs >> 7) add svg as built-in mime type >> >> looking forward to a great merge. >> >> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
