diff --git a/Pearlception/app/models/oyster.rb b/Pearlception/app/models/oyster.rb
new file mode 100644
index 0000000..7600c3a
--- /dev/null
+++ b/Pearlception/app/models/oyster.rb
@@ -0,0 +1,4 @@
+class Oyster < ActiveRecord::Base
+    establish_connection("stats")
+    
+end
diff --git a/Pearlception/config/database.yml b/Pearlception/config/database.yml
index 140a8da..835347d 100644
--- a/Pearlception/config/database.yml
+++ b/Pearlception/config/database.yml
@@ -21,8 +21,8 @@ stats:
   adapter: mysql2
   encoding: utf8
   pool: 5
-  username: ivauser
-  password: ivapassword
+  username: <%= ENV['DB_USER'] %> 
+  password: <%= ENV['DB_PASS'] %>
   host: taylors.c02zesysnssi.us-west-2.rds.amazonaws.com
   port: 3306
   database: taylors
diff --git a/Pearlception/db/schema.rb b/Pearlception/db/schema.rb
new file mode 100644
index 0000000..52ab025
--- /dev/null
+++ b/Pearlception/db/schema.rb
@@ -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 that you check this file into your version control system.
+
+ActiveRecord::Schema.define(version: 0) do
+
+end