See the Sinatra page on the website (http://ironruby.net/documentation). You need to apply two small changes since Sinatra depends on stack traces to find the entry point script. I consider this a incorrect way to do things, so anyone who'd like to clean this patch up and get it fixed in Sinatra?
~Jimmy Sent from my phone On Jul 13, 2009, at 10:11 AM, "Ivan Porto Carrero" <[email protected]<mailto:[email protected]>> wrote: I can't offer any help but I can confirm that it doesn't work for me either. --- Met vriendelijke groeten - Best regards - Salutations Ivan Porto Carrero On Mon, Jul 13, 2009 at 6:52 PM, Mark Wilkins <<mailto:[email protected]>[email protected]<mailto:[email protected]>> wrote: After finally watching John Lam's PDC presentation, I thought I'd take my IronRuby a step farther and try using it to run Sinatra. I've used Sinatra a bit with MRI, but the behavior I'm getting with IronRuby seems a bit odd. Here's what's currently installed on my machine: IronRuby 0.6.0.0 Sinatra 0.9.2 (installed via igem install) so, given a simple app like: #myapp.rb require 'rubygems' require 'sinatra' get '/' do 'hello' end 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] $ and there is no server running at localhost:4567. Anyone have any ideas? Thanks, Mark _______________________________________________ Ironruby-core mailing list <mailto:[email protected]>[email protected]<mailto:[email protected]> <http://rubyforge.org/mailman/listinfo/ironruby-core>http://rubyforge.org/mailman/listinfo/ironruby-core _______________________________________________ Ironruby-core mailing list [email protected]<mailto:[email protected]> http://rubyforge.org/mailman/listinfo/ironruby-core
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
