Yep, that will bypass the need for Sinatra to use stack traces to find the entry point script, so using a config.ru will work unpatched.
~Jimmy Sent from my phone On Jul 13, 2009, at 10:22 AM, "Mark Wilkins" <[email protected]> wrote: > On Mon, Jul 13, 2009 at 12:52 PM, Mark > Wilkins<[email protected]> wrote: >> ... >> and from the command line, running: >> $ ir myapp.rb >> >> rather than getting the expected, "==Sinatra has taken the >> stage...", I get: >> >> $ir -v myapp.rb >> IronRuby 0.6.0.0 on .NET 2.0.0.0 >> >> [E:\...@archive\devlocal\ir_dev] >> $ >> ... > > > So I just tried this, and it seems to work. > > I created a config.ru file: > > #config.ru > require 'myapp' > run Sinatra::Application > > and then started the app this way: > > $irackup config.ru (note: irackup, not rackup) > [2009-07-13 13:05:42] INFO WEBrick 1.3.1 > [2009-07-13 13:05:42] INFO ruby 1.8.6 (2008-05-28) [i386-mswin32] > [2009-07-13 13:05:42] INFO WEBrick::HTTPServer#start: pid=2964 > port=9292 > ... > > So, I'm happy with that. > > Thanks, > > Mark > _______________________________________________ > Ironruby-core mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/ironruby-core > _______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
