Ezra Zygmuntowicz wrote:
> Hello Friends-
>
>
> Merb is an ORM agnostic web framework. Its the VC layer of MVC. There
> is official plugin support for using ActiveRecord, DataMapper or
> Sequel as your ORM or you can use merb with no ORM if you want to use
> a file store or CouchDB or something like that.
>
> Merb is written with the motto of less magick in the code and clean
> modular entry points to extend the framework for your own purposes.
> Plugins are just rubygems so they support versioning and dependencies.
> We've taken a lot of the good things we like from rails and left
> behind a lot of the cruft and baggage we didn't need or want. This
> means merb is lean and mean and the code is easy to grok.
>
> Cheers-
> - Ezra Zygmuntowicz & The Merb Team
What is the best approach for converting a web app that is using Mongrel
to one that utilizes Merb?
Do I rebuild everything from scratch, or is there an example of
converting an application to Merb that would wrap an existing
mongrel/rails app in the Merb framework?
If I rebuild, is there an order I should follow when merging the models,
controllers, and views that I already have with the ones created by Merb.
Thanks in advance for your informed advice.
-- Steve Downie