Tyson Tate wrote:
> No dice. I installed SWIG and rebuilt sqlite3-ruby to no avail. I'm
> still getting the same errors.
Just to be clear, that error means that at some level ActiveRecord
(the database mapping layer that Instiki uses, part of the Rails
framework) failed to be able to access a properly set up database.
My next guess would be that the sqlite3 database isn't being properly
initialized and/or used by the server. My next question: have you
found and followed the full instructions in the README file in the
Instiki 0.11.0 distribution? There's one rather important mistake in
there that I'll point out:
Step 8: "Execute 'rake migrate'" should really be:
rake environment RAILS_ENV=production migrate
Also, I recommend running instiki as:
cd your/instiki-dir
script/server -e production
Specifying the "production" environment to these commands ensures
that the sqlite3 database is initialized and then used by the
server. Otherwise Rails defaults to the development environment,
which is configured to point to a mysql database that you probably
don't have or want to bother with.
Hope that helps,
John
P.S. If that doesn't cut it, I'll try to migrate my OS X 0.10.2
installation over to 0.11.0
and post results here. I've been looking into other bugs, and
haven't gotten to
migration issues yet.
_______________________________________________
Instiki-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/instiki-users
