Changesets can be listed by changeset number.
The Git repository is here.
- Revision:
- 381
- Log:
Radiant is now packaged as a Gem - see Changeset #373, Changeset #374,
Changeset #375, Changeset #376, Changeset #377, Changeset #378,
Changeset #379 and Changeset #380. The application part of Radiant is
now mostly empty; it exists to provide a structure which hooks into the
gem and which provides a framework for extensions. Included in this big
changeset are all the deletions, additions and changes needed to go from
the old ROOL customised Radiant to a new ROOL customised Radiant, which
includes several custom extensions adapted from the old Radiant
modifications and requires Radiant 0.9.1 to be installed as a gem.
- Author:
- rool
- Date:
- Mon Mar 21 14:01:18 +0000 2011
- Size:
- 1345 Bytes
1 | |
2 | == Installation and Setup |
3 | |
4 | Once you have extracted the files into the directory where you would like to |
5 | install Radiant: |
6 | |
7 | 1. Create the MySQL/PostgreSQL/SQLite/SQL Server/DB2 databases for your Web |
8 | site. You only need to create the "production" database, but you may also |
9 | want to create the "development" and "test" databases if you are developing |
10 | extensions or running tests. |
11 | |
12 | 2. Edit config/database.yml to taste. There are example files available for |
13 | various databases in the config directory. |
14 | |
15 | 3. Run the database bootstrap rake task: |
16 | |
17 | % rake production db:bootstrap |
18 | |
19 | (If you would like bootstrap your development database run `rake |
20 | development db:bootstrap`.) |
21 | |
22 | If you get the error "no such file to load -- spec/rake/spectask" please |
23 | install Rspec (gem install rspec). |
24 | |
25 | 4. Start it like a normal Rails application. To test execute: |
26 | |
27 | % script/server -e production |
28 | |
29 | And open your Web browser on port 3000 (http://localhost:3000). The |
30 | administrative interface is available at /admin/. By default the bootstrap |
31 | rake task creates a user called "admin" with a password of "radiant". |
32 | |
33 | When using Radiant on a production system you may also need to set permissions |
34 | on the public and cache directories so that your Web server can access those |
35 | directories with the user that it runs under. |