Forum: Ruby on Rails Ansuz CMS

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Josh A. (Guest)
on 2008-12-31 05:05
(Received via mailing list)
Hello everyone,

I just wanted to introduce Ansuz (a rails-based Content Management
System, sort of aiming for the wordpress-y space for the rails jet
set).  It's BSD licensed, and you can find it at
or  There was an article
in the 2008 Advent Calendar about it, and Akita mentioned it once in
his blog, but other than that I don't believe it's received any
visibility whatsoever.

It does have extensive plugin support using engines, theming
capabilities thanks to theme_support (as well as a way to install
themes from the master theme repository at from within
the admin interface).  It also has a crowdsound widget in the admin,
so anyone using it ever can just easily report issues or feature
suggestions.  We've got a lighthouse if you find a bug, also linked
from within the admin interface.  I'm constantly sitting in #ansuz on
FreeNode, as well as some other users and developers, available for
support / to compliment your haircut.  I'll talk you through
installing it, whatev.

It's been successfully run in a host of environments, my ubuntu/mysql
to Lex's AIX/DB2, on the mac, and I think windows (shudder).  It
currently hosts the site as well as my company's site at  If anyone ever wants to talk about it or
learn how parts of it work, or be walked through it step by step, or
whatever...we're here :)  It's got a decent number of plugins as well.

Anyway, hoping some people will join in the development.  Have a happy
new year's.

Josh Adams

PS - at first I sent this to the really old rails mailing list that's
been dead for two years-ish.  Oops.
Ryan B. (Guest)
on 2008-12-31 05:17
(Received via mailing list)
The code for the forums controller looks suspiciously like Beast's.
Perhaps a little bit of attribution credit wouldn't go astray?
Ryan B.
Josh A. (Guest)
on 2008-12-31 05:33
(Received via mailing list)
I absolutely used the savage beast plugin.  It is in vendor/plugins.
I copied over the controller to the main app to fix a few ansuz-
specific issues in it.

Sorry if you felt I was leading you astray.  Should I prominently
credit it if my project uses it?  Where should I place this credit?
I'm just trying to make sure I do alright :)

Josh A. (Guest)
on 2008-12-31 05:37
(Received via mailing list)
I've attributed the forums in the features section to savage_beast.  I
am aware that savage_beast is a clone of beast, and intend that
attribution to trickle upwards.

I really should update it to use aep_beast from I

Josh A. (Guest)
on 2008-12-31 05:38
(Received via mailing list)
Ryan B. (Guest)
on 2008-12-31 05:38
(Received via mailing list)
Looks good, thanks.
Martin N. (Guest)
on 2008-12-31 16:45
(Received via mailing list)

i tried to install it following your guide at
I had to create my databases manually using mysqladmin before I could
install the required gems.
I got them installed but when running
 > rake gems
I get the following error:
  - [I] calendar_date_select
     - [ ] hoe >= 1.8.0
     - [ ] rubyforge >= 1.0.1
     - [I] rake = 0.8.3
  - [F] mislav-will_paginate ~> 2.3.2
     - [I] activesupport = 2.2.2
  - [I] RedCloth
rake aborted!
You have a nil object when you didn't expect it!
The error occurred while evaluating nil.dependencies

(See full trace by running task with --trace)

My installed gems are:
$ gem list

*** LOCAL GEMS ***

actionmailer (2.2.2, 2.1.2, 2.1.1, 2.1.0)
actionpack (2.2.2, 2.1.2, 2.1.1, 2.1.0)
activerecord (2.2.2, 2.1.2, 2.1.1, 2.1.0)
activeresource (2.2.2, 2.1.2, 2.1.1, 2.1.0)
activesupport (2.2.2, 2.1.2, 2.1.1, 2.1.0)
arrayfields (4.6.0, 4.5.0)
attributes (5.0.1)
calendar_date_select (1.13)
cgi_multipart_eof_fix (2.5.0)
chronic (0.2.3)
coderay (0.8.260,
daemons (1.0.10)
fastthread (1.0.1)
fattr (1.0.3)
gem_plugin (0.2.3)
git-rails (0.2.1)
haml (2.0.6)
hoe (1.8.2, 1.7.0)
hpricot (0.6.164)
linecache (0.43)
main (2.8.3, 2.8.2, 2.8.0)
maruku (0.5.9)
mislav-will_paginate (2.3.2)
mocha (0.9.3, 0.9.2, 0.9.0)
mongrel (1.1.5)
rails (2.2.2, 2.1.2, 2.1.1, 2.1.0)
rake (0.8.3, 0.8.1)
RedCloth (4.1.1)
rexml-expansion-fix (1.0.1, 1.0.0)
rmagick (2.8.0, 2.7.2, 2.5.2)
rspec (1.1.11)
rspec-rails (1.1.11)
ruby-debug-base (0.10.3, 0.10.2, 0.10.1, 0.10.0)
ruby-debug-ide (0.4.3, 0.4.1, 0.2.0, 0.1.10)
rubyforge (1.0.1, 1.0.0)
rubyist-aasm (2.0.5)
ryanb-acts-as-list (0.1.2)
ryanb-factory_girl (1.1.2)
sqlite3-ruby (1.2.4, 1.2.2)
syntax (1.0.0)
thoughtbot-factory_girl (1.1.2)
tzinfo (0.3.12, 0.3.9)
ZenTest (3.11.0)

Any idea?

Josh A. (Guest)
on 2008-12-31 19:21
(Received via mailing list)

I'd actually never ran rake gems before, so I hadn't seen that.  I get
the same thing on my machine, but rake gems:install successfully
installed the ones I needed and it runs fine.  I'll look into why that

If you ignore that, does it work for you?

Josh A. (Guest)
on 2008-12-31 20:08
(Received via mailing list)
Actually, I know exactly what it is :)

Bug in rails, patch on the ticket, I'll just let ansuz get it when
rails fixes it.

Martin N. (Guest)
on 2009-01-01 20:37
(Received via mailing list)
Hi Josh,

> I'd actually never ran rake gems before, so I hadn't seen that.  I get
> the same thing on my machine, but rake gems:install successfully
> installed the ones I needed and it runs fine.  I'll look into why that
> happens.

thanks for your help and the hint in your other posting.

> If you ignore that, does it work for you?

No, I stumbled across some problems with the fckeditor ("unknown error
creating folder" etc) and a file not found error after creating a new
page. But I haven't searched too deep. I came across the mentioned
(might-be) gem problem. So I stopped my search for the reason. But now
I'll dig in deeper ;-)

Josh A. (Guest)
on 2009-01-02 15:16
(Received via mailing list)
The instructions on the site cover the fckeditor folder creation, I
actually don't like it existing in the project because when I deploy I
symlink it, but that's clearly the kind of thing other people using
the project can tell me (add the folder, modify my deploy script to
remove it and sym it to shared).  Anyway, thanks for trying it out :)

This topic is locked and can not be replied to.