Discource-C
/
discourse
mirror of https://github.com/discourse/discourse.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
discourse/config/database.yml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

62 lines
2.0 KiB
YAML
Raw Normal View History

Introduction of Chef to Vagrant. Removed redis.yml and database.yml. Also updated instructions a lot, and included setup instructions for provisioning your own VM. Closes #28 and #61.
2013-02-12 11:18:59 -05:00
development:
PERF: disable prepared statements see: https://github.com/rails/rails/issues/21992
2015-10-18 23:02:22 -04:00
prepared_statements: false
Introduction of Chef to Vagrant. Removed redis.yml and database.yml. Also updated instructions a lot, and included setup instructions for provisioning your own VM. Closes #28 and #61.
2013-02-12 11:18:59 -05:00
adapter: postgresql
Switch Development Database via ENV var This is useful if you use multiple development databases locally and don't want to constantly `db:drop db:create` into `discourse_development`. Simply add `DISCOURSE_DEV_DB=whatever_db` as an ENV variable and Discourse will use it in development mode.
2017-09-04 12:14:34 -04:00
database: <%= ENV['DISCOURSE_DEV_DB'] || 'discourse_development' %>
Remove unusued site_settings, show checkbox in UI for boolean values, remove restrict_access boolean to avoid locking yourself out by setting access_password to empty string. Minor UI tweaks.
2013-03-01 12:45:25 -05:00
min_messages: warning
FIX: Use exact patht to ensure we always redirect with the right format.
2017-09-26 23:55:06 -04:00
pool: 5
Introduction of Chef to Vagrant. Removed redis.yml and database.yml. Also updated instructions a lot, and included setup instructions for provisioning your own VM. Closes #28 and #61.
2013-02-12 11:18:59 -05:00
timeout: 5000
Support user defined postgres timeouts
2017-10-27 09:59:30 -04:00
checkout_timeout: <%= ENV['CHECKOUT_TIMEOUT'] || 5 %>
DEV: Disable migration advisory locks in dev and test environment. There is a bug in Rails that leaks an idle PG session which will prevent the dropping of the database.
2020-08-25 02:20:58 -04:00
advisory_locks: false # Disable until https://github.com/rails/rails/issues/40029 has beeen resolved.
Introduction of Chef to Vagrant. Removed redis.yml and database.yml. Also updated instructions a lot, and included setup instructions for provisioning your own VM. Closes #28 and #61.
2013-02-12 11:18:59 -05:00
host_names:
Add comment in database.yml samples about port number
2013-12-06 11:01:22 -05:00
### Don't include the port number here. Change the "port" site setting instead, at /admin/site_settings.
warns sysadmin to rebake all the posts when changing the hostname
2013-08-01 16:24:55 -04:00
### If you change this setting you will need to
### - restart sidekiq if you change this setting
### - rebake all to posts using: `RAILS_ENV=production bundle exec rake posts:rebake`
Introduction of Chef to Vagrant. Removed redis.yml and database.yml. Also updated instructions a lot, and included setup instructions for provisioning your own VM. Closes #28 and #61.
2013-02-12 11:18:59 -05:00
- "localhost"
FEATURE: allow setting postgres connection variables via environment
2021-04-14 11:34:28 -04:00
variables: <%= ENV.filter { |k,v| k.start_with? 'DISCOURSE_DB_VARIABLES_' }
.transform_keys { |k| k.slice(('DISCOURSE_DB_VARIABLES_'.length)..).downcase }
.to_json %>
Introduction of Chef to Vagrant. Removed redis.yml and database.yml. Also updated instructions a lot, and included setup instructions for provisioning your own VM. Closes #28 and #61.
2013-02-12 11:18:59 -05:00
# Warning: The database defined as "test" will be erased and
# re-generated from your development database when you run "rake".
# Do not set this db to the same as development or production.
DEV: correct parallel specs rake tasks This used to work due to side effects. `rake parallel:migrate` used to work very inconsistently and would only migrate some of the databases. This introduces the recommended change to db.yml so the correct database is found based off TEST_ENV_NUMBER if for some reason we did not set it using RAILS_DB Also avoids a bunch of schema dumping which is not needed when migrating parallel specs DB number 1 is very odd cause for whatever reason parallel spec is not setting it.
2019-12-30 22:07:44 -05:00
<%
test_db = ENV["RAILS_DB"]
if !test_db.present?
test_db = "discourse_test"
if num = ENV["TEST_ENV_NUMBER"]
num = num.presence || "1"
test_db += "_#{num}"
end
end
%>
Introduction of Chef to Vagrant. Removed redis.yml and database.yml. Also updated instructions a lot, and included setup instructions for provisioning your own VM. Closes #28 and #61.
2013-02-12 11:18:59 -05:00
test:
Make PgSQL happy ("ActiveRecord::StatementInvalid: PG::ProtocolViolation"). See https://meta.discourse.org/t/install-error-protocol-violation-with-postgresql/35160
2016-03-29 14:41:13 -04:00
prepared_statements: false
Introduction of Chef to Vagrant. Removed redis.yml and database.yml. Also updated instructions a lot, and included setup instructions for provisioning your own VM. Closes #28 and #61.
2013-02-12 11:18:59 -05:00
adapter: postgresql
DEV: correct parallel specs rake tasks This used to work due to side effects. `rake parallel:migrate` used to work very inconsistently and would only migrate some of the databases. This introduces the recommended change to db.yml so the correct database is found based off TEST_ENV_NUMBER if for some reason we did not set it using RAILS_DB Also avoids a bunch of schema dumping which is not needed when migrating parallel specs DB number 1 is very odd cause for whatever reason parallel spec is not setting it.
2019-12-30 22:07:44 -05:00
database: <%= test_db %>
Remove unusued site_settings, show checkbox in UI for boolean values, remove restrict_access boolean to avoid locking yourself out by setting access_password to empty string. Minor UI tweaks.
2013-03-01 12:45:25 -05:00
min_messages: warning
FIX: Use exact patht to ensure we always redirect with the right format.
2017-09-26 23:55:06 -04:00
pool: 5
Introduction of Chef to Vagrant. Removed redis.yml and database.yml. Also updated instructions a lot, and included setup instructions for provisioning your own VM. Closes #28 and #61.
2013-02-12 11:18:59 -05:00
timeout: 5000
DEV: Disable migration advisory locks in dev and test environment. There is a bug in Rails that leaks an idle PG session which will prevent the dropping of the database.
2020-08-25 02:20:58 -04:00
advisory_locks: false # Disable until https://github.com/rails/rails/issues/40029 has beeen resolved.
Introduction of Chef to Vagrant. Removed redis.yml and database.yml. Also updated instructions a lot, and included setup instructions for provisioning your own VM. Closes #28 and #61.
2013-02-12 11:18:59 -05:00
host_names:
- test.localhost
fixed a spelling benchamarking -> benchmarking
2014-08-14 00:46:57 -04:00
# profile db is used for benchmarking using the script/bench.rb script
added profile environment for perftools profiling (1.9.3 only)
2013-03-10 20:21:56 -04:00
profile:
PERF: disable prepared statements see: https://github.com/rails/rails/issues/21992
2015-10-18 23:02:22 -04:00
prepared_statements: false
added profile environment for perftools profiling (1.9.3 only)
2013-03-10 20:21:56 -04:00
adapter: postgresql
Create profile db generator for use when benchmarking a local install http://meta.discourse.org/t/benchmarking-discourse-locally/9070
2013-08-04 17:22:00 -04:00
database: discourse_profile
added profile environment for perftools profiling (1.9.3 only)
2013-03-10 20:21:56 -04:00
min_messages: warning
pool: 5
timeout: 5000
host_names:
- "localhost"
Source DB config more cleanly, fixes issues with socket in prd
2014-01-14 00:59:55 -05:00
# You may be surprised production is not here, it is sourced from application.rb using a monkey patch
# This is done for 2 reasons
#
# 1. we need to support blank settings correctly and rendering nothing in yaml/erb is a PITA
# 2. why go from object -> yaml -> object, pointless