Skip to content
Browse files

update install and bootstrap help messages

[ci skip]
  • Loading branch information...
1 parent db92b55 commit df0c981e0b3cf65aa298b8c5024d2e3d8691d66d @johnmuhl johnmuhl committed Feb 10, 2012
Showing with 15 additions and 41 deletions.
  1. +6 −38 INSTALL.md
  2. +9 −3 lib/tasks/database.rake
View
44 INSTALL.md
@@ -1,42 +1,10 @@
# Installation and Setup
-Once you have extracted the files into the directory where you would like to
-install Radiant:
+From within the directory containing your Radiant instance:
-1. Change to the new application directory and run:
+1. Decide which database you want to use. SQLite is configured by default and
+ the easiest way to get started. If you want to use another database:
+ - Enable your preferred database adapter in the Gemfile
+ - Run `bundle update`
- % bundle install
-
-to create a gem bundle containing all of the radiant app's dependencies.
-Whenever you edit the Gemfile to add new extensions, run `bundle install`
-again.
-
-2. Decide what database you want to use. Radiant ships with a SQLite
-configuration that will let you try it out. For serious use you will probably
-want to use on of the other supported databases: MySQL, PostgreSQL, SQL Server
-or DB2. This is the time to set up the database, grant permissions and edit
-config/database.yml to match.
-
-3. Run the database bootstrap rake task:
-
- % bundle exec rake production db:bootstrap
-
-(If you would like bootstrap a development database run `bundle exec rake db:bootstrap`.)
-
-4. Radiant is a normal Rails application and you can run it in all the usual
-ways. To test your installation, try running:
-
- % script/server production
-
-And type this address into a web browser:
-
- http://localhost:3000
-
-The administrative interface is available at /admin/. If your site is empty,
-you will be directed there automatically to create a home page. By default the
-bootstrap rake task creates a user called "admin" with a password of
-"radiant".
-
-When using Radiant on a production system you may also need to set permissions
-on the public and cache directories so that your Web server can access those
-directories with the user that it runs under.
+2. Run `bundle exec rake production db:bootstrap` to initialize the database
View
12 lib/tasks/database.rake
@@ -49,12 +49,18 @@ namespace :db do
Rake::Task['db:migrate:extensions'].invoke
Rake::Task['radiant:extensions:update_all'].invoke
puts %{
+Your Radiant application is ready to use. Run `script/server -e production` to
+start the server. Your site will then be running at http://localhost:3000
-Your radiant application is now complete. You can test it by running script/server and directing a web browser to http://localhost:3000/.
+You can access the administrative interface at http://localhost:3000/admin
-To add radiant extensions, just add gem lines to your application's Gemfile and run bundle install again.
+You may also need to set permissions on the public and cache directories so that
+your Web server can access those directories with the user that it runs under.
-To find radiant extensions, please visit http://ext.radiantcms.org.
+To add more extensions just add them to your Gemfile and run `bundle install`.
+If an extension is not available as a gem use `script/extension install name`.
+
+Visit http://ext.radiantcms.org to find more extensions.
}
end

0 comments on commit df0c981

Please sign in to comment.
Something went wrong with that request. Please try again.