diff --git a/.pg_migrate b/.pg_migrate
new file mode 100644
index 000000000..14b242c75
--- /dev/null
+++ b/.pg_migrate
@@ -0,0 +1,2 @@
+build.connopts=dbname:jam_db_build
+build.oob_connopts=dbname:postgres
diff --git a/Gemfile b/Gemfile
index cd0d1e58f..51aea59d7 100644
--- a/Gemfile
+++ b/Gemfile
@@ -7,4 +7,4 @@ workspace = ENV["WORKSPACE"] || "workspace"
 # $ cd [workspace]
 # $ git clone https://github.com/sethcall/pg_migrate_ruby
 
-gem 'pg_migrate', '0.1.0'  #:path=> '~/' + workspace + '/pg_migrate_ruby'
+gem 'pg_migrate', '0.1.3' # :path=> '~/' + workspace + '/pg_migrate_ruby'
diff --git a/Gemfile.lock b/Gemfile.lock
index bc687e3d3..9d1fd49f0 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -5,7 +5,7 @@ GEM
     logging (1.7.2)
       little-plugger (>= 1.1.3)
     pg (0.14.0)
-    pg_migrate (0.1.0)
+    pg_migrate (0.1.3)
       logging (= 1.7.2)
       pg (= 0.14.0)
       thor (= 0.15.4)
@@ -15,4 +15,4 @@ PLATFORMS
   ruby
 
 DEPENDENCIES
-  pg_migrate (= 0.1.0)
+  pg_migrate (= 0.1.3)
diff --git a/README b/README
index 8347f8130..f004f8c04 100644
--- a/README
+++ b/README
@@ -15,6 +15,9 @@ Environment
 * bash . If on windows, use git bash or cygwin. Bash is used as the build script technology.  (could change very easily)
 * Definition of location for your developer workspace. Default is ~/workspace, but if you define an env variable, you can override.
 * pg_migrate_ruby - $ cd [workspace] && git clone https://github.com/sethcall/pg_migrate_ruby
+* you want it so the current user has access to the 'postgres' database and is a super user.  In other words, you want to make sure your current logged in user can do the following at the command line: 'psql postgres'.  If you can do that, you should be OK.  There are two reasons this may not work for you.  
+# Your current user is not a superuser.  If not, do `sudo su postgres -c "createuser YOURUSER"`  and answer 'y' with the first question.
+# If your user already is a superuser, then the postgres database may not exist yet. In that case, do `psql` then `create database postgres`
 * NOT YET: $IVY defined as path to the [apache ivy jar](http://ant.apache.org/ivy/download.cgi). Download the latest ivy from here, extract somewhere, and create an IVY environment variable with a path to the ivy.jar. For example, in my bash.profile: `export IVY=/Users/seth/workspace/apache-ivy-2.3.0-rc1/ivy-2.3.0-rc1.jar`
 
 Building
diff --git a/build b/build
index 301096623..8e504f306 100755
--- a/build
+++ b/build
@@ -21,7 +21,7 @@ mkdir -p $PG_RUBY_PACKAGE_OUT
 bundle update
 
 echo "building migrations"
-bundle exec pg_migrate build --source . --out $PG_BUILD_OUT
+bundle exec pg_migrate build --source . --out $PG_BUILD_OUT --test
 
 echo "packaging migrations for ruby"bundle exec pg_migrate package --source $PG_BUILD_OUT --out $PG_RUBY_PACKAGE_OUT --name jam-db --version "0.0.1"
 bundle exec pg_migrate package --source $PG_BUILD_OUT --out $PG_RUBY_PACKAGE_OUT --name $PROJECT_NAME --version $BUILD_NUMBER
diff --git a/manifest b/manifest
index e69de29bb..bb357703a 100644
--- a/manifest
+++ b/manifest
@@ -0,0 +1 @@
+sessions.sql