Make production environment work

config/database.yml

@@ -21,11 +21,10 @@ default: &default
   host: db
   username: <%= ENV['POSTGRES_USER'] %>
   password: <%= ENV['POSTGRES_PASSWORD'] %>
+  database: <%= ENV['POSTGRES_USER'] %>
 
 development:
   <<: *default
-  database: app_development
-
   # The specified database role being used to connect to postgres.
   # To create additional roles in postgres see `$ createuser --help`.
   # When left blank, postgres will use the default role. This is
@@ -59,7 +58,7 @@ development:
 test:
   <<: *default
   database: app_test
-
+  
 # As with config/credentials.yml, you never want to store sensitive information,
 # like your database password, in your source code. If your source code is
 # ever seen by anyone, they now have access to your database.
@@ -81,4 +80,3 @@ test:
 #
 production:
   <<: *default
-  database: app_production

config/environments/production.rb

@@ -20,7 +20,7 @@ Rails.application.configure do
 
   # Disable serving static files from the `/public` folder by default since
   # Apache or NGINX already handles this.
-  config.public_file_server.enabled = ENV['RAILS_SERVE_STATIC_FILES'].present?
+  config.public_file_server.enabled = true
 
   # Compress CSS using a preprocessor.
   # config.assets.css_compressor = :sass

config/secrets.yml

@@ -0,0 +1,16 @@
+# Be sure to restart your server when you change the secret.
+
+# Your secret key is used for verifying the integrity of signed cookies.
+# If you change this key, all old signed cookies will become invalid!
+
+# Make sure the secret is at least 30 characters and all random,
+# no regular words or you'll be exposed to dictionary attacks.
+
+development:
+  secret_key_base: <%= ENV['SECRET_KEY_BASE'] %>
+
+test:
+  secret_key_base: <%= ENV['SECRET_KEY_BASE'] %>
+
+production:
+  secret_key_base: <%= ENV['SECRET_KEY_BASE'] %>