From 270620682c1a3c006af4f9d15f9be58537d4d9ee Mon Sep 17 00:00:00 2001 From: hellekin Date: Mon, 5 Oct 2020 14:29:11 +0200 Subject: Create database setup --- config/database.yml | 5 +++++ db/schema.rb | 18 ++++++++++++++++++ 2 files changed, 23 insertions(+) create mode 100644 db/schema.rb diff --git a/config/database.yml b/config/database.yml index bfc1d74..233210c 100644 --- a/config/database.yml +++ b/config/database.yml @@ -20,6 +20,11 @@ default: &default # For details on connection pooling, see Rails configuration guide # https://guides.rubyonrails.org/configuring.html#database-pooling pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %> + host: <%= ENV.fetch("DATABASE_HOST", "db") %> + database: <%= ENV.fetch("POSTGRES_DB", "the_map_db") %> + username: <%= ENV.fetch("POSTGRES_USER", "postgres") %> + password: <%= ENV.fetch("POSTGRES_PASSWORD", "postgres") %> + development: <<: *default diff --git a/db/schema.rb b/db/schema.rb new file mode 100644 index 0000000..b10373b --- /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 `rails +# db:schema:load`. When creating a new database, `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 -- cgit v1.2.3