eBooru/config/database.yml

default: &default
  adapter: postgresql
  timeout: 5000
  username: e621

development:
  <<: *default
  database: e621_development
  host: postgres
  pool: 5

test:
  <<: *default
  database: e621_test
  host: postgres
  pool: 5

<% if Rails.env.production? %>
production:
  <<: *default
  database: e621
  password: <%= ENV.fetch("DB_PASSWORD") %>
  host: <%= ENV.fetch("DB_HOST") %>
  port: <%= ENV.fetch("DB_PORT") %>
  pool: <%= Sidekiq.server? ? ENV.fetch("DB_WORKER_POOL_SIZE") : ENV.fetch("DB_POOL_SIZE") %>
<% end %>
[CI] Commit database.yml Makes the test setup easier. Also eases prod deploys with the two separate db pool sizes. 2023-02-25 08:41:07 -05:00			`default: &default`
			`adapter: postgresql`
			`timeout: 5000`
[DB] Upgrade to postgres 15 Execute the following commands, before pulling: docker-compose up -d docker-compose exec postgres pg_dump danbooru2 -U danbooru > backup.sql docker-compose down docker volume rm e621ng_db_data Execute the following commands, after pulling: docker-compose up -d docker-compose exec -T postgres psql -d e621_development -U e621 < backup.sql This also changes the name of the database and role. Now seems like a nice opportunity to do so. 2023-03-01 14:31:49 -05:00			`username: e621`
[CI] Commit database.yml Makes the test setup easier. Also eases prod deploys with the two separate db pool sizes. 2023-02-25 08:41:07 -05:00
			`development:`
			`<<: *default`
[DB] Upgrade to postgres 15 Execute the following commands, before pulling: docker-compose up -d docker-compose exec postgres pg_dump danbooru2 -U danbooru > backup.sql docker-compose down docker volume rm e621ng_db_data Execute the following commands, after pulling: docker-compose up -d docker-compose exec -T postgres psql -d e621_development -U e621 < backup.sql This also changes the name of the database and role. Now seems like a nice opportunity to do so. 2023-03-01 14:31:49 -05:00			`database: e621_development`
[CI] Commit database.yml Makes the test setup easier. Also eases prod deploys with the two separate db pool sizes. 2023-02-25 08:41:07 -05:00			`host: postgres`
			`pool: 5`

			`test:`
			`<<: *default`
[DB] Upgrade to postgres 15 Execute the following commands, before pulling: docker-compose up -d docker-compose exec postgres pg_dump danbooru2 -U danbooru > backup.sql docker-compose down docker volume rm e621ng_db_data Execute the following commands, after pulling: docker-compose up -d docker-compose exec -T postgres psql -d e621_development -U e621 < backup.sql This also changes the name of the database and role. Now seems like a nice opportunity to do so. 2023-03-01 14:31:49 -05:00			`database: e621_test`
[CI] Commit database.yml Makes the test setup easier. Also eases prod deploys with the two separate db pool sizes. 2023-02-25 08:41:07 -05:00			`host: postgres`
			`pool: 5`

[DB] Only evaluate prod config on prod Fixup for https://github.com/e621ng/e621ng/commit/b43f0cbbb0cc130d2aac31dd1ddb411b3a1bff16 2023-02-28 09:48:42 -05:00			`<% if Rails.env.production? %>`
[CI] Commit database.yml Makes the test setup easier. Also eases prod deploys with the two separate db pool sizes. 2023-02-25 08:41:07 -05:00			`production:`
			`<<: *default`
			`database: e621`
[DB] Loudly fail on prod when DB env variables aren't set 2023-02-28 09:38:34 -05:00			`password: <%= ENV.fetch("DB_PASSWORD") %>`
			`host: <%= ENV.fetch("DB_HOST") %>`
[DB] Make the port configurable 2023-03-13 19:27:43 -04:00			`port: <%= ENV.fetch("DB_PORT") %>`
[DB] Loudly fail on prod when DB env variables aren't set 2023-02-28 09:38:34 -05:00			`pool: <%= Sidekiq.server? ? ENV.fetch("DB_WORKER_POOL_SIZE") : ENV.fetch("DB_POOL_SIZE") %>`
[DB] Only evaluate prod config on prod Fixup for https://github.com/e621ng/e621ng/commit/b43f0cbbb0cc130d2aac31dd1ddb411b3a1bff16 2023-02-28 09:48:42 -05:00			`<% end %>`