From ed14042feac6ff84670958fc3e2017aaacac5856 Mon Sep 17 00:00:00 2001 From: David Heinemeier Hansson Date: Mon, 6 Dec 2004 18:19:56 +0000 Subject: Cleaned it up git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@50 5ecf4fe2-1ee6-0310-87b1-e25e094e27de --- railties/doc/index.html | 49 ++++++++++++------------------------------------- 1 file changed, 12 insertions(+), 37 deletions(-) diff --git a/railties/doc/index.html b/railties/doc/index.html index 25f1061d11..b40b9562ea 100644 --- a/railties/doc/index.html +++ b/railties/doc/index.html @@ -27,13 +27,9 @@ -

Congratulations, you're on Rails!

+

Congratulations, you've put Ruby on Rails!

-

- You've succesfully configured your web server to point at this Rails application. -

- -

Before you move on, verify that the following conditions have been met:

+

Before you move on, verify that the following conditions have been met:

  1. The log directory and the empty log files must be writable to the web server (chmod -R 777 log). @@ -53,43 +49,22 @@

    Take the following steps to get started:

      -
    1. Create empty production and test databases for your application.
      - Warning: Don't point your test database at your production database, it'll destroy the latter on test runs! +
    2. Create empty development and test databases for your application.
      + Recommendation: Use *_development and *_test names, such as basecamp_development and basecamp_test
      + Warning: Don't point your test database at your development database, it'll destroy the latter on test runs!
    3. Edit config/database.yml with your database settings. -
    4. Create a new controller using the script/new_controller generator
      - Help: Run with no arguments for documentation -
    5. Create a new model using the script/new_model generator
      - Help: Run with no arguments for documentation -
    6. See all the tests run and fail by running rake. +
    7. Create controllers and models using the generators in script/new_*
      + Help: Run a generator with no arguments for documentation +
    8. See all the tests run by running rake.
    9. Develop your Rails application! -
    10. Setup FastCGI or mod_ruby to get production-level performance +
    11. Setup Apache with FastCGI (and Ruby bindings), if you need better performance

    - Having problems getting up and running? First try debugging it yourself by looking at the log files.
    Then try the friendly Rails - community on IRC (howto IRC). It's on FreeNode, in channel - #rubyonrails. + Having problems getting up and running? First try debugging it yourself by looking at the log files.
    + Then try the friendly Rails community on the web or on IRC + (FreeNode#rubyonrails).

    -
    -

    Rails Online

    - - -
    - -
    -

    Beyond CGI

    - - -
    - \ No newline at end of file -- cgit v1.2.3