<?xml version="1.0" encoding="UTF-8"?>
<page>
  <created-at type="datetime">2009-03-23T11:51:36Z</created-at>
  <description></description>
  <id type="integer">1116</id>
  <name>Radiant_CMS</name>
  <number type="integer">2</number>
  <person-id type="integer">6645</person-id>
  <text>Radiant CMS is an elegant, lightweight content management system built upon the popular Ruby on Rails framework and serves eg. the [http://www.ruby-lang.org Ruby Programming Language website] itself. 

For more information on Radiant, please visit the [http://radiantcms.org Radiant website].

==Getting Radiant==

The easiest and recommended way of getting Radiant CMS is via RubyGems.

  jruby -S gem install radiant

==Bootstrapping==

In your projects directory issue an application generator command. In this example I'll use the jdbcmysql adapter and my application name will be radiantblog.

  jruby -S radiant --database=mysql radiantblog

To set up the database connections edit radiantblog/config/database.yml and create the database as well.

  production:
    adapter: jdbcmysql
    database: radiantblog_production
    username: usr
    password: passwd
    host: localhost

You can omit to set up other database configurations for now and correct it later.

  jruby -S rake production db:bootstrap

The bootstrap task will populate your database and set up a basic administration and page system based on your answers to the setup questions in the terminal. To start your application issue the familiar Rails command.

  jruby script/server -e production

Fire up your browser and play around a little with your new CMS - [http://localhost:3000]

==Deployment==

My first deployment was under a Tomcat 6 with the [[Warbler]] gem.

  jruby -S warble config

My minimal config file is as follows.

  Warbler::Config.new do |config|
    config.dirs = %w(cache config db log vendor tmp)
    config.gems += [&quot;activerecord-jdbcmysql-adapter&quot;, &quot;radiant&quot;]
    config.gem_dependencies = true
    config.war_name = &quot;ROOT&quot;
  end

I set the war name to ROOT to avoid the problems with the default Radiant routing and assets including.

  jruby -S warble:war

Deploy your generated war file under Tomcat's webapps folder, start the server and check http://localhost:8080 for your CMS.
</text>
  <text-as-html>&lt;p&gt;Radiant CMS is an elegant, lightweight content management system built upon the popular Ruby on Rails framework and serves eg. the &lt;a class='external' href=&quot;http://www.ruby-lang.org&quot;&gt;Ruby Programming Language website&lt;/a&gt; itself. 

&lt;/p&gt;&lt;p&gt;For more information on Radiant, please visit the &lt;a class='external' href=&quot;http://radiantcms.org&quot;&gt;Radiant website&lt;/a&gt;.

&lt;/p&gt;&lt;h2&gt;&lt;a name='Getting_Radiant'&gt;&lt;/a&gt;Getting Radiant&lt;/h2&gt;
&lt;p&gt;
The easiest and recommended way of getting Radiant CMS is via RubyGems.

&lt;/p&gt;&lt;pre&gt;  jruby -S gem install radiant
&lt;/pre&gt;&lt;h2&gt;&lt;a name='Bootstrapping'&gt;&lt;/a&gt;Bootstrapping&lt;/h2&gt;
&lt;p&gt;
In your projects directory issue an application generator command. In this example I'll use the jdbcmysql adapter and my application name will be radiantblog.

&lt;/p&gt;&lt;pre&gt;  jruby -S radiant --database=mysql radiantblog
&lt;/pre&gt;&lt;p&gt;
To set up the database connections edit radiantblog/config/database.yml and create the database as well.

&lt;/p&gt;&lt;pre&gt;  production:
    adapter: jdbcmysql
    database: radiantblog_production
    username: usr
    password: passwd
    host: localhost
&lt;/pre&gt;&lt;p&gt;
You can omit to set up other database configurations for now and correct it later.

&lt;/p&gt;&lt;pre&gt;  jruby -S rake production db:bootstrap
&lt;/pre&gt;&lt;p&gt;
The bootstrap task will populate your database and set up a basic administration and page system based on your answers to the setup questions in the terminal. To start your application issue the familiar Rails command.

&lt;/p&gt;&lt;pre&gt;  jruby script/server -e production
&lt;/pre&gt;&lt;p&gt;
Fire up your browser and play around a little with your new CMS - &lt;a class='external' href=&quot;http://localhost:3000&quot;&gt;http://localhost:3000&lt;/a&gt;

&lt;/p&gt;&lt;h2&gt;&lt;a name='Deployment'&gt;&lt;/a&gt;Deployment&lt;/h2&gt;
&lt;p&gt;
My first deployment was under a Tomcat 6 with the &lt;a href='&lt;?url_for_page Warbler?&gt;' class='internal'&gt;Warbler&lt;/a&gt; gem.

&lt;/p&gt;&lt;pre&gt;  jruby -S warble config
&lt;/pre&gt;&lt;p&gt;
My minimal config file is as follows.

&lt;/p&gt;&lt;pre&gt;  Warbler::Config.new do |config|
    config.dirs = %w(cache config db log vendor tmp)
    config.gems += [&amp;quot;activerecord-jdbcmysql-adapter&amp;quot;, &amp;quot;radiant&amp;quot;]
    config.gem_dependencies = true
    config.war_name = &amp;quot;ROOT&amp;quot;
  end
&lt;/pre&gt;&lt;p&gt;
I set the war name to ROOT to avoid the problems with the default Radiant routing and assets including.

&lt;/p&gt;&lt;pre&gt;  jruby -S warble:war
&lt;/pre&gt;&lt;p&gt;
Deploy your generated war file under Tomcat's webapps folder, start the server and check &lt;a class='external' href=&quot;http://localhost&quot;&gt;http://localhost&lt;/a&gt;:8080 for your CMS.
&lt;/p&gt;</text-as-html>
  <updated-at type="datetime">2009-04-29T08:29:54Z</updated-at>
  <wiki-id type="integer">320</wiki-id>
</page>
