Looks like it's time for another release of Radiant: http://radiantcms.org/download/ This is a minor update in the 0.6 series. The primary benefit to it is that people using Sean Cribb’s Page Attachements extension can now use it without running on edge. WHAT IS RADIANT CMS? Radiant is a no-fluff content management system made for designers and programmers and is ideal for use on small teams. It is similar to Movable Type or Textpattern, but is much more than a blogging engine. Radiant features: * An elegant user interface * The ability to arrange pages in a hierarchy * Flexible templating with layouts, snippets, page parts, and a custom tagging language (Radius: http://radius.rubyforge.org) * A dynamic extension system * A simple user management/permissions system * Support for Markdown and Textile as well as traditional HTML (it's easy to create other filters) * Operates in two modes: dev and production depending on the URL * A caching system which expires pages every 5 minutes * Built using Ruby on Rails (which means that extending Radiant is as easy as any other Rails application) * Licensed under the MIT-License * And much more... There's even a live demo over on the project Web site: http://radiantcms.org/demo/ WHAT'S NEW IN THIS RELEASE? * Removed some of the database specific code from the ArchiveFinder [Daniel S.] * Fixed typo in extension model generator documentation * Reworked the way the generator extension is loaded (closing #500) [Keita] * Fixed failing unit tests in instance mode [Daniel Shephard] * Modified the page edit form to use multipart/form-data (useful for an upload extension) [Sean C.] INSTALLATION We've worked hard to make it easy to install Radiant. For starters you can download it with Ruby Gems: % gem install --include-dependencies radiant Once the Radiant gem is installed you have access to the `radiant` command. The `radiant` command is similar to the `rails` command (if you are from the Rails world. It's how you generate a new Radiant project for a website. So `cd` to the directory where you would like your instance to be installed and type: % radiant -d [mysql|postgres|sqlite3] . Next, edit config/database.yml to taste. Then run the rake bootstrap task: % rake production db:bootstrap And start up the test server: % script/server -e production Finally, hit the /admin/ URL and you should be off to the races. See the README file in the release for additional details. If you are interested in other download options, visit the download page: http://radiantcms.org/download/. UPGRADING FROM 0.6.x 1. Update the Radiant gem: % gem update radiant 2. Change the RADIANT_GEM_VERSION constant in config/environment.rb to "0.6.1". 3. Run the update rake task: rake radiant:update 4. Restart the server UPGRADING FROM 0.5.x The upgrade process changed significantly from last release, so listen up! To upgrade an existing installation, BACKUP YOUR DATABASE, update the gem, and create a new Radiant project using the instructions above. Then point Radiant to the right database by editing config/database.yml and execute the following command in your project directory: % rake db:migrate If you have problems during the upgrade, please let us know. CONTRIBUTORS Radiant wouldn't be possible without the help of some fine people. The following people have made contributions to this release: * Daniel S. * Sean C. * Keita Thanks guys! If you'd like to hop on the development band wagon head on over to our dev site (http://dev.radiantcms.org/). SUPPORT The best place to get support is definitely on the Radiant mailing list. There's a crowd of people there who have been hanging around for many moons now. Newbie questions are welcome! To sign up, go to: http://radiantcms.org/mailing-list/ The Radiant mailing list is also accessible via Ruby forum: http://www.ruby-forum.com/forum/21 Enjoy! -- John L. http://wiseheartdesign.com http://radiantcms.org
on 2007-06-24 07:47
on 2007-07-02 12:29
On Sunday 24 June 2007 05.46, John W. Long wrote: > Looks like it's time for another release of Radiant: > > http://radiantcms.org/download/ Ii would be nice with a separate announcement list for new releases, updates and other "official" information. Or, alternatively, if there is an announcement list, I would like some help finding it. Keep up the good work, /Jonas
on 2007-07-02 13:09
Jonas Eliasson wrote: > Keep up the good work, > I wonder if there really is a need for it? The main Radiant list is quite low bandwidth (at least compared to the Rails list I am also on) and it's easy to set up a filter for the announcements. Also, there aren't really that many announcements to justify a separate list, IMHO. On the other hand, if people think it's useful, I'm all for it :) Cheers, Mohit. 7/2/2007 | 5:07 PM.
on 2007-07-02 17:44
>> a separate announcement list for new releases, updates and other >> "official" information. I think this is a great idea.
on 2007-07-02 17:59
I think that it's a good idea. Right now I'm focusing on radiant sites and it's good to read the list mail. Most of the time I am not and delete them before reading them. If there were a separate list I could filter them easily. Erik
on 2007-07-02 21:06
I disagree. Our list traffic, while healthy lately, has been far from overwhelming. If you want announcements only, I suggest filtering out everything but [ANN] posts. That is the purpose of that convention -- so you can quickly see what the post is about. We also have the weblog, while scarcely used lately, it is generally a good place to see announcements from the core team. Sean
on 2007-07-02 22:01
Sean, I didn't know that ANN stood for Announcement, sorry. I thought it was some sort of cruff the list picked up. - Erik