Instiki<\/a> is one of the premier wikis for Ruby on Rails<\/a> which is another way of saying the other rails-based solutions don’t look that great so far from what I’ve seen. Here is an except from the instiki website:<\/p>\n \n 1. Download Yeah, nice and simple… to install<\/b>. Here’s some facts that instiki DOESN’T tell you without digging around:<\/p>\n So what does this all mean? Well, if you want to migrate your instiki<\/a> instance to a different instance you’d like to think you have a couple of options.<\/p>\n Option #1 works quite well however if you want to switch database backends you’re stuck with option #2. However save yourself hours of time (I didn’t) and DON’T<\/b> try the following things (unless you’re a rails god. In which case why are you reading this?)<\/p>\n Now I’m sure DHH<\/a> (the creator of instiki) will grumble about something about this not being ‘appropriate’ for its original intentions and blah-blah. Gee that’s nice. Maybe you better put that down in the caveats, before I commit a whole bunch of data into it.<\/p>\n Okay, enough ranting about half-baked Open Source Rails apps. Here’s the fix.<\/p>\n Most normal rails app will include a file called plugin inside $RAILS_ROOT\/script\/plugin. Unfortunately, instiki doesn’t include it. Luckily the script is really small since it just calls out to the rails framework to handle most of the hardwork. So try this:<\/p>\n \nI’m afraid I don’t have time to explain what a Rails Fixture<\/a> is in this post but just think of it as a portable way of representing data going into a database for rails. It works well but don’t try hundreds of megabytes of data.\n<\/p>\n \nI also won’t go much into rails plugins<\/a> except to say it’s a way of extending a rails application with more functionality (probably for a Rails developer rather than an end user of the application). We’re going to use a really sweet tool called manage_fixtures<\/a> which allows us to move around data between different databases with ease (assuming the rails app isn’t doing weird SQL crap).\n<\/p>\n The following will export all your db entries as fixtures into $INSTIKI_HOME\/test\/fixtures<\/em>. You need to set the RAILS_ENV to production because by default it will try to use the development database.<\/p>\n Now change the file in $INSTIKI_HOME\/config\/databases.yml<\/em> from:<\/p>\n to the following (adjust mysql parameters to suit your setup)<\/p>\n The following commands will create a database named instiki (or whatever you put in databases.yml) and make sure the database schema in the database matches instiki’s schema.<\/p>\n Whew! Finally we can re-import the data into MySQL (or whatever) and continue on using instiki for something.<\/p>\n The Rant Instiki is one of the premier wikis for Ruby on Rails which is another way of saying the other rails-based solutions don’t look that great so far from what I’ve seen. Here is an except from the instiki website: 1. Download 2. Run \u201cinstiki\u201d with Ruby 1.8.4 or greater. (on windows, that\u2019s instiki.cmd) […]<\/p>\n","protected":false},"author":703,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1216,1215,615,260],"tags":[],"class_list":["post-588","post","type-post","status-publish","format-standard","hentry","category-fixes","category-gripe","category-ruby","category-tech"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/posts\/588","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/users\/703"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/comments?post=588"}],"version-history":[{"count":0,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/posts\/588\/revisions"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/media?parent=588"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/categories?post=588"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/tags?post=588"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n 2. Run \u201cinstiki\u201d with Ruby 1.8.4 or greater. (on windows, that\u2019s instiki.cmd)
\n 3. Chuckle\u2026 There Is No Step Three\u2122! \ud83d\ude42 (See note) \n<\/p><\/blockquote>\n\n
\n
\n
\nto find where the issue might be. Don’t worry, even the changelogs say import is busted and there is no other sign of some way to input data easily<\/li>\nThe Fix<\/h3>\n
1. Add plugin script to instiki app<\/h5>\n
\n
\r\n$ echo \"\r\n#!\/usr\/bin\/env ruby\r\nrequire File.dirname(__FILE__) + '\/..\/config\/boot'\r\nrequire 'commands\/plugin'\r\n\" >> $INSTIKI_HOME\/script\/plugins\r\n$ chmod +x $INSTIKI_HOME\/script\/plugin # Make it executable\r\n<\/pre>\n<\/blockquote>\n
2. Install the manage_fixtures<\/a> plugin<\/h5>\n
\n
\r\n$ cd $INSTIKI_HOME\r\n$ script\/plugin discover # Hit enter a gazillion times\r\n$ script\/plugin install manage_fixtures\r\n<\/pre>\n<\/blockquote>\n
3. Export the data into fixtures<\/h5>\n
\n
\r\n$ cd $INSTIKI_HOME # You SHOULD be here anyways\r\n$ RAILS_ENV='production' rake db:fixtures:export_all\r\n<\/pre>\n<\/blockquote>\n
4. Change the database connection to desired<\/h5>\n
\n
\r\nproduction:\r\n adapter: sqlite3\r\n database: db\/production.db.sqlite3\r\n<\/pre>\n<\/blockquote>\n
\n
\r\nproduction:\r\n adapter: mysql\r\n host: localhost\r\n database: instiki\r\n username: root\r\n password:\r\n<\/pre>\n<\/blockquote>\n
4. Create database and the appropriate tables<\/h5>\n
\n
\r\n$ echo \"create database instiki\" | mysql -u root\r\n$ RAILS_ENV='production' rake migrate\r\n<\/pre>\n<\/blockquote>\n
5. Finally re-import the data from fixtures<\/h5>\n
\n
\r\n$ RAILS_ENV='production' rake db:fixtures:import_all\r\n<\/pre>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"