Thank you very much for the reply. I did see the method you mentioned, unfortunately, that's not quite what I'm after. I apologize for not being clear :-)
I want to be able to load as much of the application framework, plug-ins and gems as possible, and then pause, waiting for a test run request to be received. As soon as a test run request is received, I want to fork the process, and then load the rest of the application code (models, controllers, Lib, etc.). The point of this is to reduce the amount of time it takes to run your specs (I'm not sure if you have seen the spork project, but it's the successor of the rspec DRb server. The way that I'm accomplishing what I wanted rails is by trapping certain methods, and basically turning calls to them into procs, which are stored away and called after the processes forked. I hope I'm explaining myself clearly :-) Thanks, Tim On Wed, Jun 24, 2009 at 5:28 PM, Matt Aimonetti <[email protected]> wrote: > > Hi Tim, > > In your config/init.rb file you will find a block looking like that: > > Merb::BootLoader.after_app_loads do > # This will get executed after your app's classes have been loaded. > end > > > This is where you need to put the code you want to load after the app is > loaded :) > > - Matt > > On Wed, Jun 24, 2009 at 4:17 PM, Tim Harper <[email protected]> wrote: >> >> I'm working on Spork support for merb, and am needing to prevent merb from >> preloading application code when loading the environment. Basically, I want >> to be able to load all of merb, it's gems, and it's plugins, and then start >> listening for spec-run requests. When a spec run request is receive, spork >> will then fork itself, and load the application files as needed. >> I'm not a merb developer, so I'm without a clue. Is there a standard >> configuration parameter to do this? How do you run a merb server in >> development mode, or do you? >> Any guidance will be very appreciated >> Thanks! >> Tim >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
