I'm going to give RubyForge a try, now that I've got it set up for hosting the .gem file. I've got the bare minimum set up there -- the important one being the Tracker. For the time being, I'm going to continue to host the documentation here.

Also, for the time being, I'm going to defer installing Trac, just until I see how well things go with using RubyForge.

If you've found a bug, or you have a feature request, please check out the Yurt CMS RubyForge page

Things to Watch Out For

One of the things that tripped me up after releasing YurtCMS 0.1.0 was the idea that people's Ruby installation could be in a place different than my preset /usr/local/bin/ruby, which caused some consternation. After a bit of research, I learned about the existence of /usr/bin/env and how to use it.

However, using /usr/bin/env will not work in all cases -- there is no guarantee that it will pick the correct version of Ruby to run if you have multiple installations. If you're being bit by this particular error, please go into the following files in the gem install location (/path/to/ruby/gems/1.8/gems/YurtCMS-0.x.0):

bin/yurt
site/yurt/yurt.cgi
test/cms_filesystem.rb
test/cms_strings.rb

and update the #! line to match the correct path.