Radiant CMS

[Lord Bodak]

Anyone tried using Radiant CMS here?

I've been messing with it and it took an interesting concoction to get it working.

I had to:
Copy the .htaccess, dispatch.rb, dispatch.cgi, dispatch.fcgi from a project generated with ocs-install-rails (not too surprising)
Give 777 permissions to the cache/, db/, and /tmp/sessions/ directories
Give 666 permissions to the files in cache/ and db/

After doing that, everything works, but being on a shared host I certainly don't want to have a bunch of files world-writable. I'm assuming the problem is due to Apache running as a different user than myself, but I'm not sure what the solution is.

In addition, if I change .htaccess to run dispatch.fcgi instead of dispatch.cgi, I get an error that the database could not be opened (it's SQLite).

Learning a little bit at a time here :)

--Mike

[rob]

You don't have to do this if you use Lighttpd or have mongrel running on a port we assign through Apache. This is probably your best bet, as you don't have to chase down dispatchers and deal with sometimes wonky permissions :)

[Lord Bodak]

I know performance would be better that way, so once I get things a bit more stable I'll probably make the switch.

[BoulderAnalytics.com]

Hi,

I was able to Radiant working on OCS for a couple of sites. I highly recommend using webmin/lighttpd. I plan on writing a how-to this weekend. Until then, you should be able to follow the install steps with the following pointers.

On Webmin/lighttpd, it is not necessary to install the radiant gem as it is already installed(thanks, Rob).

1 Use "radiant -u path" to install with the unpack option in your desired directory.
2 Create the DB user and Databases(Radiant prod,dev,test).
3 Create/Modify the Database.yml file. This part requires some OCS specific changes:

production:
adapter: mysql
database: radiant_prod
username: mysqluser.domain
password: password
socket: /var/run/mysqld/mysqld.sock

4 Run the script/setup_database production
5 Test installation using script/server webrick -e production
View site at http://yourdomain:3000

Additional steps for Lighttpd
6 Request Lighttpd port for Radiant Install
7 Modify lighttpd.conf using search/replace per OCS instructions.
8 Start lighttpd instance using ./start-lighttpd.conf
View site at http://yourdomain.com


Bryan
http://BoulderAnalytics.com

Official Radiant Installation instructions:
http://dev.radiantcms.org/radiant/wiki/Installation

[Lord Bodak]

I've done all of that except the lighttpd (probably will do so once I'm a little farther along), and unpacking Radiant. It is working fine without the unpacked Radiant instance, so I don't see any reason to unpack it.

[BoulderAnalytics.com]

Hi,

The unpack option actually creates an application install not instance(I'll revise original post). It isn't necessary, but that is how I have done most of my installations.

Thanks,

Bryan

http://www.boulderanalytics.com

[rob]

Thank you very much for the info. I'll move this to a new post, make sticky, and copy this to a guide in tech support.