diff --git a/.github/workflows/deploy_heroku.yml b/.github/workflows/deploy_heroku.yml
index dd010c4..a164a3c 100644
--- a/.github/workflows/deploy_heroku.yml
+++ b/.github/workflows/deploy_heroku.yml
@@ -15,7 +15,7 @@ on:
 env:
   DOCKER_REGISTRY_HOST: ${{ secrets.DOCKER_REGISTRY_HOST }}
   DOCKER_REGISTRY_USERNAME: ${{ github.repository_owner }}
-  DOCKER_REGISTRY_TOKEN: ${{ secrets.DOCKER_REGISTRY_TOKEN }}
+  DOCKER_REGISTRY_TOKEN: ${{ secrets.GITHUB_TOKEN }}
   DOCKER_IMAGE: ${{ github.repository }}
   HEROKU_API_KEY: ${{ secrets.HEROKU_API_KEY }}
 
@@ -42,9 +42,9 @@ jobs:
         run: |
           if [[ $BRANCH_TAG = "latest" ]]
           then
-            echo "HEROKU_APP=rails_view_component_blog" >> $GITHUB_ENV
+            echo "HEROKU_APP=view-component-blog" >> $GITHUB_ENV
           else
-            echo "HEROKU_APP=rails_view_component_blog-staging" >> $GITHUB_ENV
+            echo "HEROKU_APP=view-component-blog-staging" >> $GITHUB_ENV
           fi
 
       - name: Login to Docker registry
diff --git a/db/schema.rb b/db/schema.rb
new file mode 100644
index 0000000..4603022
--- /dev/null
+++ b/db/schema.rb
@@ -0,0 +1,18 @@
+# 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.
+#
+# This file is the source Rails uses to define your schema when running `bin/rails
+# db:schema:load`. When creating a new database, `bin/rails db:schema:load` tends to
+# be faster and is potentially less error prone than running all of your
+# migrations from scratch. Old migrations may fail to apply correctly if those
+# migrations use external dependencies or application code.
+#
+# It's strongly recommended that you check this file into your version control system.
+
+ActiveRecord::Schema.define(version: 0) do
+
+  # These are extensions that must be enabled in order to support this database
+  enable_extension "plpgsql"
+
+end