# Recent Posts by distler

72 posts found

 posted 3 months ago distler 72 posts edited 3 months ago Forum: Instiki – Topic: installation problems (mac osx lion) Well, that was fun… I think I have instiki now running successfully on Ruby 1.8.7 Ruby 1.9.3 Ruby 2.0.0 It was quite a juggling act getting it to work on all three. But I think I’ve succeeded. Let me know if you encounter further problems. (In an attempt to eat my own dogfood, I have switched this forum and the copy of Instiki running on Golem, to run under Ruby 2.0.0.) posted 3 months ago distler 72 posts edited 3 months ago Forum: Instiki – Topic: installation problems (mac osx lion) I actually had tried the development version, too… Please try again. The relevant feature of the development version is that it changes. (only I was prompted to update Ruby when I first tried to run the bundler; which I did; my current version is 2.0.0) Oh! I haven’t tested Instiki on Ruby 2.0. Works fine on 1.9.x, but there may be issues with 2.0. posted 3 months ago distler 72 posts Forum: Instiki – Topic: installation problems (mac osx lion) Thanks for the bug report. The latest development version ( .tar.gz, bzr or git) should fix this problem. posted 6 months ago distler 72 posts Forum: Instiki – Topic: Bugs Since I’ve not had much success reproducing your bug, why don’t we see whether implementing your suggestion fixes it for you? Apply the following patch:  === modified file 'app/controllers/revision_sweeper.rb' --- app/controllers/revision_sweeper.rb 2011-09-21 04:46:36 +0000 +++ app/controllers/revision_sweeper.rb 2013-05-30 05:11:33 +0000 @@ -7,15 +7,15 @@ observe Revision, Page def before_save(record) - if record.is_a?(Revision) - expire_cached_page(record.page.web, record.page.name) - expire_cached_revisions(record.page) + if record.is_a?(Page) + expire_cached_page(record.web, record.name) + expire_cached_revisions(record) end end def after_save(record) - if record.is_a?(Revision) - expire_caches(record.page) + if record.is_a?(Page) + expire_caches(record) end end  posted 7 months ago distler 72 posts Forum: Instiki – Topic: Bugs I put 2.9.1 in the Gemfile but I don’t know if that’s the minimum value. Might as well assume that 2.9.1 is the minimum (since we know that it works). I updated the instructions accordingly. Interestingly, bundle won’t update to the latest version unless you specify such a minimum. Correct. If you don’t specify a version, then any version is supposed to suffice. posted 7 months ago distler 72 posts Forum: Instiki – Topic: Bugs Poking around, I discovered that my fresh install was using version 2.9.1 of the mysql gem but the live installs were using 2.8.1. If there’s a minimum version number for the gem that we should be using (no version number is currently specified), then that would be good to know, so that the Gemfile can be updated, accordingly. Curious, though, that this “cache bug” of yours would seem to have nothing to do with … caching. posted 7 months ago distler 72 posts Forum: Instiki – Topic: Windows installation not working So any tips on migrating an already running wiki on a different server? The advantage of SQLite3 is that the entire database is in a single file, db/production.db.sqlite3 … which makes it easy to transfer.  bundle exec rake upgrade_instiki  will, among other things, perform the necessary database migrations (assuming the previous one is not too old). posted 7 months ago distler 72 posts Forum: Instiki – Topic: Windows installation not working Never had so much trouble for something that is supposed to be so simple.. ugh.. Hopefully, you pain will be someone else’s gain, if the Windows installation instructions can be improved, based on your experience. However looks like every gem listed on the gem file i have to install manually… I don’t understand.  bundle install –path vendor/bundle  doesn’t install the gems in in the vendor/bundle/ruby/* ? Or it does install them, but then Instiki can’t find them? posted 7 months ago distler 72 posts Forum: Instiki – Topic: Windows installation not working The sqlite3 rubygem won’t compile without thelibsqlite3 C-library. (Unlike many rubygems, which are pure Ruby, this one contains a C extension that links to the aforementioned library.) Windows (unlike other operating systems) doesn’t come with that library installed. Some Ruby installers, for Windows, install it; evidently, some don’t. For those, you’ll have to install it yourself. If you google around, you’ll find plenty of useful advice on this topic. Unfortunately (since i don’t have any familiarity with Windows), I’m not a useful source for such advice. But, yes, as far as I can tell, installing the Windows SQLite3 package is a prerequisite for getting the sqlite3 rubygem installed. How does this installation work? What i gather you use “GIT” to download all the packages or i think bundles is the term and then ruby installs them on the system? Bundler lets you manage/install rubygems, without installing them on the system. Instead, they are installed in your application’s vendor/bundle directory. But that’s not where (as far as I can tell) your problem lies. posted 7 months ago distler 72 posts Forum: Instiki – Topic: Windows installation not working I don’t know what Ruby installation you have for Windows, but presumably, you are missing the SQLite3 precompiled binaries for Windows. Presumably, the Windows Installation Instructions could be improved. posted 8 months ago distler 72 posts Forum: Instiki – Topic: instiki without database? I’m not sure why you think the Madeleine Persistence Layer (which, I believe, is what 0.9.2 uses) is lighter-weight than Sqlite3. You do need to store the data somewhere. And, with Sqlite3, there’s no separate database process the data is stored in a single file, db/production.db.sqlite3. posted 8 months ago distler 72 posts Forum: Instiki – Topic: instiki without database? No. You need some database. But the default sqlite3 is as lightweight as humanly possible. posted 8 months ago distler 72 posts Forum: Instiki – Topic: Feature Requests posted 8 months ago distler 72 posts Forum: Instiki – Topic: problem running instiki after installation Probably, those instructions are out-of-date. (Help updating them would be appreciated.) It would be best to ensure that you have a fully-functioning Ruby (1.9.3 is preferable) installation before proceeding with getting Instiki running. Perhaps these instructions might help. posted 8 months ago distler 72 posts Forum: Instiki – Topic: problem running instiki after installation I followed all the instructions on your installation page for ubuntu. What page are you talking about? posted 9 months ago distler 72 posts Forum: Instiki – Topic: Feature Requests It’s been suggested that this is because that is in a div with class name byline. That seems a pretty thin reed on which to base a request for changing the class names we use. Google is pretty cagey about what algorithms they use. I’m kinda dubious about this one. posted 9 months ago distler 72 posts edited 9 months ago Forum: Instiki – Topic: Bugs I am fairly certain that none of my recent updates would affect this scenario.. But I’m happy to hear that it fixed itself. posted 9 months ago distler 72 posts Forum: Instiki – Topic: migration to Rails3. This is extremely interesting. Porting Instiki to Rails3 has long been on my TODO list. But (as you’ve seen), it’s not a small job. So it keeps getting pushed back in favour of other things. So I’m really happy you’re working on this! posted 9 months ago distler 72 posts Forum: Instiki – Topic: Bugs Pandoc is clearly weird. But you have uncovered a regression in Maruku. I’ve fixed that bug in the latest version in my repository on Github.  ruby bundle update will fix the problem. posted 9 months ago distler 72 posts Forum: Instiki – Topic: Migration from Textile Interesting question! I guess the first question is: do you want to convert the whole history (ie all previous revisions of each page) to Markdown, or just the current version? If you just need the current version converted, you can go to the “Export” tab, and click on “Markup” to create a zip archive containing the (Textile) markup of each page. If you want to convert the previous revisions, too, then you should look at the rake tasks described on this page. Those instructions are geared towards migrating from one database (e.g. sqlite) to another (e.g. MySQL). But they would also be useful in converting the content of the revisions table, without changing database engines. The db:fixtures:export_all rake task dumps your database to a (series of) YAML file(s). db:fixtures:import_all imports them to a (new) database. In between, you’d run a conversion on the dump/fixtures/revisions.yml file. posted 10 months ago distler 72 posts Forum: Instiki – Topic: Bugs I’m sorry. Could you please distill that long and rambling discussion in to a set of steps by which one might reproduce the bug? posted 10 months ago distler 72 posts Forum: Instiki – Topic: Instiki website The instiki.org website is a hopeless mess, on many levels. Alas, I don’t control it, so I can’t do much about it (except to send the occasional plaintive email message to Matthias, which he ignores). Instead, point your browser at my website, which contains both up-to-date information and (as best as I am able to assure) is spam-free. posted about 1 year ago distler 72 posts Forum: Instiki – Topic: Bugs Sorry, I follow exactly the steps you outlined, and it’s adequate+subcategory (and its variants) that get cleared from the cache, not adequate+subcategory+>+history. The scenario you outline (involving the old name being forgotten before the cache gets swept) is exactly what the before_save action is supposed to avoid. Then the cache gets swept again in an after_save action. Now, the only thing I can think of is that I tested this under SQLite3, rather than MySQL. Perhaps the driver for the latter does something funky. But that seems unlikely… posted about 1 year ago distler 72 posts Forum: Instiki – Topic: Debugging uninterruptible sleep It looks as though it is the “All Pages” request that is clogging up the works, … at 7000 pages then it’s a bit cumbersome, to say the least, I have no idea why that would be an issue. It’s not as if Instiki has to do anything with those 7000 pages, apart from retrieving an alphabetical list of their names (and URLs). If that’s indeed your problem, it would be nice to know why. posted about 1 year ago distler 72 posts Forum: Heterotic Beast – Topic: MathJax 2.0 The latest commits, to Heterotic Beast, upgrade it to MathJax 2.0 (from 1.1). This loads (a little) faster, and also sports a SVG rendering option (selectable from the context menu). posted about 1 year ago distler 72 posts Forum: Instiki – Topic: MathJax 2.0 The latest commits, to Instiki, upgrade it to MathJax 2.0 (from 1.1). This loads (a little) faster, and also sports a SVG rendering option (selectable from the context menu). posted over 1 year ago distler 72 posts Forum: Instiki – Topic: Bugs Hmmm. Both look wrong. What I think we want is: table_name = f.gsub( Regexp.new(Regexp.escape(Rails.root.join('dump','fixtures').to_s + File::SEPARATOR)), '').gsub('.yml', '') The point being that the output of Regexp.escape is a (properly-escaped) string which is suitable as input to Regexp.new. posted over 1 year ago distler 72 posts Forum: Instiki – Topic: Bugs If you’ve found a mistake in the rake` task, please send me a patch. posted over 1 year ago distler 72 posts Forum: Heterotic Beast – Topic: MySQL Gotcha If you’re going to use Heterotic Beast in production, you need to be running MySQL 5.5.3 or later, and follow the advice in this blog post. Otherwise, the lack of support for Unicode will come back to bite you. posted over 1 year ago distler 72 posts Forum: itex2MML – Topic: weird math fonts P.S.: Congratulations on figuring out how to make this page ill-formed! It took a bit of work to fix the issue.