Instiki

List Poster wrote:

Using http://rubyforge.org/frs/download.php/66872/rubyinstaller-1.9.1-p243-rc1.exe

Instiki output:

C:parasew-instiki-7e61bc1>ruby.exe scriptserver -e production => Booting WEBrick => Rails 2.3.5 application starting on http://0.0.0.0:2500 => Call with -d to detach => Ctrl-C to shutdown server [2009-12-28 13:33:09] INFO WEBrick 1.3.1 [2009-12-28 13:33:09] INFO ruby 1.9.1 (2009-07-16) [i386-mingw32] [2009-12-28 13:33:09] INFO WEBrick::HTTPServer#start: pid=2432 port=2500

http://localhost:2500 output:

Application error (Apache)

Something very bad just happened. I just know it. Do you smell smoke?

Hmmm. That's not very informative.

One thing to try is installing the sqlite3-ruby gem (doesn't matter whether you installed it for Ruby 1.8; you need to install it all over again for 1.9). I'm not 100% sure the "non-native" bundled version continues to work in Ruby 1.9 (though the "native" gem does work).

And, of course, there's the 'Windows-spaces-in-pathnames'-aware version of script/server. (Certainly, there will be problems if config/environment.rb doesn't get read.

Please try those two things out.

One thing to try is installing the sqlite3-ruby gem (doesn't matter whether you installed it for Ruby 1.8; you need to install it all over again for 1.9). I'm not 100% sure the "non-native" bundled version continues to work in Ruby 1.9 (though the "native" gem does work).

Without Gem: reported error.
With 'sqlite3' Gem: reported error.
With 'sqlite3-ruby' Gem: works!

So it looks like both 1.8 and 1.9 are clear if that SPECIFIC Gem is used.

And, of course, there's the 'Windows-spaces-in-pathnames'-aware version of script/server. (Certainly, there will be problems if config/environment.rb doesn't get read.

This was run without spaces as that bit still seems to be an issue.

List Poster wrote:

With 'sqlite3-ruby' Gem: works!

Great. So, it seems, the sqlite3-ruby gem is optional (on Windows) under Ruby 1.8, but required under Ruby 1.9.

And, of course, there's the 'Windows-spaces-in-pathnames'-aware version of script/server. (Certainly, there will be problems if config/environment.rb doesn't get read.

This was run without spaces as that bit still seems to be an issue.

Spaces in the pathname are going to be an issue (and not just on Windows).

I've put a note to that effect on my installation page .

I'm going to keeps this "open", as a tracker for possible issues with running Instiki under various Ruby 1.9 setups.

So far, we know

• MacOSX 10.5
  Ruby 1.9.2dev
  Passenger 2.2.8
  mysql, sqlite3, mongrel, passenger gems
  (Passenger(Apache), Mongrel, or WEBRick servers, MySQL database)
• MacOSX 10.6
  Ruby 1.9.2dev
  sqlite3, mongrel gems
  (Mongrel or WEBRick server, sqlite3 database)
• Windows (mingw32)
  Ruby 1.9.1 p243 (One-click Installer)
  sqlite3-ruby gem
  (WEBRick server, sqlite3 database)

work.

One thing you might try (if you don't mind) is doing a

gem install mongrel

Instiki will then run using the Mongrel webserver, instead of the default WEBRick. It would be nice to know that works as well.

Instiki will then run using the Mongrel webserver, instead of the default WEBRick. It would be nice to know that works as well.

Error (popup): "ruby.exe - Unable To Locate Component / This application has failed to start because msvcrt-ruby18.dll was not found. Re-installing the application may fix this problem."

I checked out your install page and it didn't seem to have the gem notes, but just to wrap it up:

1.8/mingw runs by default with a warning
1.8/mingw runs without warning if sqlite3-ruby is installed
1.9/mingw fails by default
1.9/mingw runs without warning if sqlite3-ruby is installed
1.9/mingw fails if mongrel is installed
All versions have apparent issues with spaces in the path

My suggestion is to tell Windows users to use the latest (mingw) installers, gem install sqlite3-ruby, and not run out of a directory which contains a space.

List Poster wrote:

Instiki will then run using the Mongrel webserver, instead of the default WEBRick. It would be nice to know that works as well.

Error (popup): "ruby.exe - Unable To Locate Component / This application has failed to start because msvcrt-ruby18.dll was not found. Re-installing the application may fix this problem."

That's a very strange error.

I would not have been surprised, if the Mongrel gem didn't work under Window + Ruby1.9. But I'd expect the error to be something other than not being able to find a DLL.

I checked out your install page and it didn't seem to have the gem notes,

I just added a note about that.

but just to wrap it up:

1.8/mingw runs by default with a warning 1.8/mingw runs without warning if sqlite3-ruby is installed 1.9/mingw fails by default 1.9/mingw runs without warning if sqlite3-ruby is installed 1.9/mingw fails if mongrel is installed All versions have apparent issues with spaces in the path

My suggestion is to tell Windows users to use the latest (mingw) installers, gem install sqlite3-ruby, and not run out of a directory which contains a space.

It's a wiki, so if you think my instructions can be improved, please have-at-it.

Alright, I edited it a bit :-)

I now see that this appears to be a branch rather than a dev site - should I also edit the main release site?

List Poster wrote:

Alright, I edited it a bit :-)

I now see that this appears to be a branch rather than a dev site - should I also edit the main release site?

It was a branch, until we merged them at version 0.16.3, and I became co-maintainer of the main line of Instiki.

The instiki.org site is a bit of a mess, currently. If you want to take a crack at fixing up anything there, please go ahead.