At 9:03 PM +1100 1/22/06, Assaph Mehr wrote: > I think that actually starts the production environment, for > which you haven't created the database. Either copy the dev.db > to prod.db, or start it with: > > ruby script\server -e development
That appears to work. At least, I got the "Instiki Setup" screen. I was beginning to wonder if running this under Ruby 1.8.4 was the problem. Incidentally, is that likely to be an issue? If so, can I simply avoid it by saying: /usr/bin/ruby script/server -e development where this specifically starts up the OSX 1.8.2: % ruby -v ruby 1.8.4 (2005-12-24) [powerpc-darwin8.4.0] % /usr/bin/ruby -v ruby 1.8.2 (2004-12-25) [powerpc-darwin8.0] > That's all the tests failing. ... I gathered that (:-). > My recommendation may have been inappropriate as it > seems it's been in this state from before Christmas. Could be. As a Ruby Nuby, I'm not really the person who should be trying to work on these problems (though it would certainly be a learning experience). Alexey, can you give us any idea of your plans? -r -- Technical editing and writing, programming, and web development: http://www.cfcl.com/rdm/resume Contact information: [EMAIL PROTECTED], +1 650-873-7841 _______________________________________________ Instiki-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/instiki-users
