On Dec 4, 7:56 pm, Michael Klishin <[EMAIL PROTECTED]> wrote: > On 05.12.2008, at 2:26, Jeremy Evans wrote: > > > Merb is overriding the configuration given to Merb::Config inside > > Merb.start. > > It's intentional I guess. very flat applications need to be started > with explicitly given init file path (using -I option, that's capital > i and not lowercase L). > Init file is then loaded and config is updated. > > How do you run your application?
Like the previous message shows, "ruby merb_setup.rb". I disabled the init file because Merb shouldn't need to load it, I'm doing all of the controller, model, and configuration setup myself before calling Merb.start (and if I used the init file, it would be loaded twice). The reason for this is I deploy with ruby-style, so I can't use the merb command line tool. Is it not supported to use Merb without the merb command line tool? I could probably work around the issue by putting most of the configuration in a separate file and calling "Merb.start(%w'-I merb_setup2.rb -a mongrel')" instead, I'll give that a try. That's uglier than I'd like, but I'll deal with it. I suppose I could also use the "if __FILE__ == $0" trick to keep everything in one file. Camping, Ramaze, and Sinatra all work correctly using pretty much the same thing I'm trying with Merb, FWIW. Jeremy --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
