Changesets can be listed by changeset number.
The Git repository is here.
- Revision:
- 4
- Log:
Initial import of Radiant 0.50 sources from a downloaded Tarball.
Radiant is a Ruby On Rails based lightweight content management
system.
- Author:
- adh
- Date:
- Sat Jul 22 16:47:40 +0100 2006
- Size:
- 2709 Bytes
| 1 | == Welcome to Radiant |
| 2 | |
| 3 | Radiant is a no-fluff, open source content management system designed |
| 4 | for small teams. It is similar to Textpattern or MovableType, but is |
| 5 | a general purpose content management system (not just a blogging |
| 6 | engine). |
| 7 | |
| 8 | Radiant features: |
| 9 | |
| 10 | * An elegant user interface |
| 11 | * The ability to arrange pages in a hierarchy |
| 12 | * Flexible templating with layouts, snippets, page parts, and a |
| 13 | custom tagging language (Radius: http://radius.rubyforge.org) |
| 14 | * Special page-oriented plugins called behaviors |
| 15 | * A simple user management/permissions system |
| 16 | * Support for Markdown and Textile as well as traditional HTML |
| 17 | (it's easy to create other filters) |
| 18 | * Operates in two modes: dev and production depending on the URL |
| 19 | * A caching system which expires pages every 5 minutes |
| 20 | * Built using Ruby on Rails (which means that extending Radiant is |
| 21 | as easy as any other Rails application) |
| 22 | * And much more... |
| 23 | |
| 24 | |
| 25 | == License |
| 26 | |
| 27 | Radiant is released under the MIT license and is copyright (c) 2006 |
| 28 | John W. Long. A copy of the MIT license can be found in the LICENSE |
| 29 | file. |
| 30 | |
| 31 | |
| 32 | == Installation and Setup |
| 33 | |
| 34 | Radiant is a traditional Ruby on Rails application, meaning that you |
| 35 | can configure and run it the way you would a normal Rails |
| 36 | application. |
| 37 | |
| 38 | Once you have extracted the files into the directory where you would |
| 39 | like to install Radiant: |
| 40 | |
| 41 | 1. Create a MySQL/PostgreSQL/SQLite database for your Web site. |
| 42 | |
| 43 | 2. Create config/database.yml for your database setup. (There are |
| 44 | several examples in the config directory.) |
| 45 | |
| 46 | 3. Run the database setup script: |
| 47 | |
| 48 | % script/setup_database production |
| 49 | |
| 50 | 4. Start it like a normal Rails application. To test execute: |
| 51 | |
| 52 | % script/server production |
| 53 | |
| 54 | And open your Web browser on port 3000 (http://localhost:3000). |
| 55 | |
| 56 | When using Radiant on a production system you may also need to set |
| 57 | permissions on the public and cache directories so that your Web server |
| 58 | can access those directories with the user that it runs under. |
| 59 | |
| 60 | Once you've installed Radiant on your own Web site, be sure to add your |
| 61 | name and Web site to the list of radiant users: |
| 62 | |
| 63 | http://dev.radiantcms.org/radiant/wiki/RadiantUsers |
| 64 | |
| 65 | |
| 66 | == Radiant Admin Interface |
| 67 | |
| 68 | The administrative interface is available at /admin/. By default the |
| 69 | `setup_database` script creates a user called "admin" with a password of |
| 70 | "radiant". |
| 71 | |
| 72 | |
| 73 | == Support |
| 74 | |
| 75 | The best place to get support is on the mailing list: |
| 76 | |
| 77 | http://radiantcms.org/mailing-list/ |
| 78 | |
| 79 | There is also a Trac powered dev site available here: |
| 80 | |
| 81 | http://dev.radiantcms.org/ |
| 82 | |
| 83 | Please Note: Before filing a ticket on the dev site discuss your question |
| 84 | or problem on the mailing list. This makes it much easier to manage |
| 85 | legitimate tickets. |
| 86 | |
| 87 | |
| 88 | Enjoy! |
| 89 | |
| 90 | -- |
| 91 | John Long :: http://wiseheartdesign.com |
