Permalink
Browse files

Add database component back so db:migrate doesn't fail

  • Loading branch information...
1 parent c46da42 commit 924266e274b19b0957d363e2131944b313b86774 @nicksieger nicksieger committed Mar 26, 2011
Showing with 31 additions and 6 deletions.
  1. +1 −6 config/application.rb
  2. +15 −0 config/database.yml
  3. +15 −0 db/schema.rb
View
@@ -1,11 +1,6 @@
require File.expand_path('../boot', __FILE__)
-# Pick the frameworks you want:
-# require "active_record/railtie"
-require "action_controller/railtie"
-require "action_mailer/railtie"
-require "active_resource/railtie"
-require "rails/test_unit/railtie"
+require "rails/all"
# If you have a Gemfile, require the gems listed there, including any gems
# you've limited to :test, :development, or :production.
View
@@ -0,0 +1,15 @@
+development:
+ adapter: mysql
+ database: r3test_development
+ host: localhost
+ username: root
+ password:
+ encoding: utf8
+
+production:
+ adapter: mysql
+ database: r3test
+ host: localhost
+ username: root
+ password:
+ encoding: utf8
View
@@ -0,0 +1,15 @@
+# This file is auto-generated from the current state of the database. Instead
+# of editing this file, please use the migrations feature of Active Record to
+# incrementally modify your database, and then regenerate this schema definition.
+#
+# Note that this schema.rb definition is the authoritative source for your
+# database schema. If you need to create the application database on another
+# system, you should be using db:schema:load, not running all the migrations
+# from scratch. The latter is a flawed and unsustainable approach (the more migrations
+# you'll amass, the slower it'll run and the greater likelihood for issues).
+#
+# It's strongly recommended to check this file into your version control system.
+
+ActiveRecord::Schema.define(:version => 0) do
+
+end

0 comments on commit 924266e

Please sign in to comment.