Skip to content

Commit

Permalink
Merge pull request #1114 from pulibrary/1111-postgres-upgrade
Browse files Browse the repository at this point in the history
Update ci and lando to use postgres 13
  • Loading branch information
hackartisan authored Aug 25, 2022
2 parents 95d6270 + 5ef27c8 commit ce6a2de
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 9 deletions.
6 changes: 3 additions & 3 deletions .circleci/config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -91,14 +91,14 @@ jobs:
RAILS_ENV: test
PULFALIGHT_DB_HOST: localhost
PULFALIGHT_DB_USERNAME: pulfalight
PULFALIGHT_DB_PASSWORD: ""
PULFALIGHT_DB_PASSWORD: pulfalight
SOLR_URL: http://solr:SolrRocks@localhost:8983/solr/pulfalight-core-test
- image: zookeeper:3.4
- image: postgres:10.6-alpine
- image: postgres:13.6
environment:
POSTGRES_USER: pulfalight
POSTGRES_DB: pulfalight_test
# POSTGRES_PASSWORD: ""
POSTGRES_PASSWORD: pulfalight
POSTGRES_HOST_AUTH_METHOD: trust
- image: solr:8.4
command:
Expand Down
2 changes: 1 addition & 1 deletion .lando.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ services:
config:
dir: "solr/conf"
pulfalight_database:
type: postgres:10
type: postgres:13
portforward: true
app_mount: false
proxy:
Expand Down
10 changes: 5 additions & 5 deletions db/schema.rb
Original file line number Diff line number Diff line change
Expand Up @@ -2,11 +2,11 @@
# 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).
# 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.

Expand Down

0 comments on commit ce6a2de

Please sign in to comment.