When I was playing with this stuff I just added the extra arg of the
server I wanted started:
jruby script/server webrick
-Tom
On Tue, 13 Jun 2006, Charles O Nutter defenestrated me:
>
>With the fastcgi nonsense commented out, the fcntl patch, and the
>Socket/BasicSocket thing fixed,
With the fastcgi nonsense commented out, the fcntl patch, and the Socket/BasicSocket thing fixed, script/server starts up and successfully serves the index page!!!And then it stops doing anything.But it's close!
=> Booting WEBrick...=> Rails application started on http://0.0.0.0:3000=> Ctrl-C to sh
Fixed. SocketMetaClass needed the following:- extend BasicSocketMetaClass- pass the BasicSocket rubyclass as parentSocketLibrary needed to reorder creation of BasicSocketMetaClass and SocketMetaClass so Socket could extend BasicSocket. The extension in the .rb file doesn't work unless the classes a
Perhaps this has something to do with it:irb(main):014:0> Socket.superclass=> ObjectNow we just need to figure out why that's happening :)On 6/13/06,
Charles O Nutter <[EMAIL PROTECTED]> wrote:
The Socket/BasicSocket dichotomy is certainly an interesting issue. It doesn't seem to be a simple issue
The Socket/BasicSocket dichotomy is certainly an interesting issue. It doesn't seem to be a simple issue of singleton methods, since File's singleton methods work fine in extending classes:class F < Fileend
F.dirname => wrong number of arguments (i.e. it's finding it ok)So there's something odd ab
Well, so I've found the first thing that's a problem with script/server,
at least on my win32-box. The server script first tries to determine
which server to use. It does this by all different manners of fun
tricks. This one:
if RUBY_PLATFORM !~ /mswin/ && !silence_stderr { `lighttpd -version`
}
