> to get Merb log to stdout in dev mode, and see what may fail under the > covers. Or check development env log
There isn't more information, even when I look in log/development.log. Who else could eat up my error messages? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
