<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -7,3 +7,4 @@ vendor
 doc/app
 failed
 db/development_structure.sql
+_site</diff>
      <filename>.gitignore</filename>
    </modified>
    <modified>
      <diff>@@ -16,6 +16,11 @@ To get the latest copy use one of the following:
 
   git clone git://github.com/intalio/singleshot.git
 
+You will need MySQL. The file config/databases.yml contains the connection
+configurations for the development, test and production environment. You can
+either setup MySQL accounts and databases based on this file, or change it to
+pick different database/account.
+
 To setup you development environment, specifically installing all the necessary
 dependencies and setting up the development and test databases, run the script
 script/setup:
@@ -27,50 +32,12 @@ This will also create a default account using your user name and the password
 
 To get started:
 
-  ./script server
+  ruby script/server
 
 Point your browser to http://localhost:3000 and login with your user name and
 password.
 
 
-== Setting up the database
-
-The database is configured in config/databases.yml.  The development and test
-database is set to use SQLite3, and the SQLite3 drive is installed when running
-script/setup.  For production, you should consider using something else (the
-default configuration is MySQL).
-
-
-== Migrations
-
-Rails migrations are a great way to progress from one database schema version
-to another in production.  Each major milestone or release will include a new
-set of migrations so production database can be updated by running rake
-db:migrate.
-
-Migrations are not used to move from one schema to another during daily
-development progress.  The database schema will just change and you'll have to
-recreate the entire database.
-
-Those changes are recorded in the form of migration, but to update run:
-
-  rake db:migrate:reset db:test:clone
-
-This task will recreate the entire development and test database.  In addition,
-we uses the Annotates Models gem to, well, annotate the Rails models with the
-most recent database schema.  So when changing the database schema, follow
-with:
-
-  /usr/bin/annotate 
-
-Watch the source files for changes, move the schema annotations to their
-rightful place.
-
-To recreate the dummy data used for development:
-
-  rake db:populate
-
-
 == LICENSE
 
 Singleshot  Copyright (C) 2008-2009  Intalio, Inc</diff>
      <filename>README.rdoc</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>8953b9a84c35d3af0a987dce790e257e91e92384</id>
    </parent>
  </parents>
  <author>
    <name>Assaf Arkin</name>
    <email>assaf@labnotes.org</email>
  </author>
  <url>http://github.com/intalio/singleshot/commit/893cdd09442d7d54fed0c53bf56ca794e31e9c2d</url>
  <id>893cdd09442d7d54fed0c53bf56ca794e31e9c2d</id>
  <committed-date>2009-03-19T20:11:41-07:00</committed-date>
  <authored-date>2009-03-19T20:11:41-07:00</authored-date>
  <message>Updated README to refelct that we're using MySQL and fix script name</message>
  <tree>e606e329e8397832a84a69cbbe0bbdf3e0e8c513</tree>
  <committer>
    <name>Assaf Arkin</name>
    <email>assaf@labnotes.org</email>
  </committer>
</commit>
