Hi list ! I've built a CMS based on rails. The CMS is not just another toy rails app. It's a complex application with lots of things done differently from rails for performance and design reasons. For a quick look at the project, it lives here: http://zenadmin.org.
During all the development of zena (since 2005, rails 0.x), I have been struggling with rails. I eventually stopped and froze at 1.2.6. The main issue is that there are very few things that I need to be done "the rails way". For example: fixtures. Since the beginning testing was too slow and I had to hack rails so that fixtures don't get reloaded every time. Then I decided to move on to foxy fixtures, but I cannot use the "rails way" because zena is a multi-site application and I use this fact to scope testing (scoped fixtures). Another big issue: the query helpers (defined with has_many, ...) could never be used as is because of security issues (it's not because the visitor can read Page4 that she can read Page4.children. It's now time to upgrade (1.2.6 is quite old) and I am wondering: Since zena is in fact a framework for building CMS or other tools, shouldn't I use something I would not have to fight against but could work with ? My questions: 1. Deployment: how does passenger and such work with Merb ? 2. RJS/prototype: this is used a lot, how does it work with Merb ? 3. controller filters: I like this in rails (before_filter, ...): how is this done here ? 4. testing... zena has over 1300 tests. Mostly unit tests so this should not be too much a problem I think. 5. any other issue ? Many thanks for your help... Gaspard --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
