discourse/config/database.yml

development:
  adapter: postgresql
  database: discourse_development
  min_messages: warning
  host: localhost
  pool: 5
  timeout: 5000
  host_names:
    ### Don't include the port number here. Change the "port" site setting instead, at /admin/site_settings.
    ### 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`
    - "localhost"

# 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.
test:
  adapter: postgresql
  database: discourse_test
  min_messages: warning
  host: localhost
  pool: 5
  timeout: 5000
  host_names:
    - test.localhost

# profile db is used for benchamarking using the script/bench.rb script
profile:
  adapter: postgresql
  database: discourse_profile
  min_messages: warning
  host: localhost
  pool: 5
  timeout: 5000
  host_names:
    - "localhost"

production:
  pool: <%= GlobalSetting.db_pool %>
  timeout: <%= GlobalSetting.db_timeout %>
  adapter: postgresql
  socket: <%= GlobalSetting.db_socket %>
  host: <%= GlobalSetting.db_host %>
  port: <%= GlobalSetting.db_port %>
  database: <%= GlobalSetting.db_name %>
  username: <%= GlobalSetting.db_username %>
  password: <%= GlobalSetting.db_password %>
  host_names:
    - <%= GlobalSetting.hostname %>
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:`
			`adapter: postgresql`
			`database: 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`
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: localhost`
			`pool: 5`
			`timeout: 5000`
			`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"`

			`# 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.`
			`test:`
			`adapter: postgresql`
			`database: discourse_test`
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`
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: localhost`
			`pool: 5`
			`timeout: 5000`
			`host_names:`
			`- test.localhost`

IMPORTANT - removed all sample files This is very likely to cause merge conflict, it is for the greater good Discuss at: http://meta.discourse.org/t/enough-with-the-sample-files/10351 From now on we use ENV to customise if needed 2013-12-18 00:46:37 -05:00			`# profile db is used for benchamarking 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:`
			`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`
			`host: localhost`
			`pool: 5`
			`timeout: 5000`
			`host_names:`
			`- "localhost"`
IMPORTANT - removed all sample files This is very likely to cause merge conflict, it is for the greater good Discuss at: http://meta.discourse.org/t/enough-with-the-sample-files/10351 From now on we use ENV to customise if needed 2013-12-18 00:46:37 -05:00
			`production:`
clean up config to use global settings 2013-12-19 23:12:23 -05:00			`pool: <%= GlobalSetting.db_pool %>`
			`timeout: <%= GlobalSetting.db_timeout %>`
IMPORTANT - removed all sample files This is very likely to cause merge conflict, it is for the greater good Discuss at: http://meta.discourse.org/t/enough-with-the-sample-files/10351 From now on we use ENV to customise if needed 2013-12-18 00:46:37 -05:00			`adapter: postgresql`
clean up config to use global settings 2013-12-19 23:12:23 -05:00			`socket: <%= GlobalSetting.db_socket %>`
			`host: <%= GlobalSetting.db_host %>`
			`port: <%= GlobalSetting.db_port %>`
			`database: <%= GlobalSetting.db_name %>`
			`username: <%= GlobalSetting.db_username %>`
			`password: <%= GlobalSetting.db_password %>`
IMPORTANT - removed all sample files This is very likely to cause merge conflict, it is for the greater good Discuss at: http://meta.discourse.org/t/enough-with-the-sample-files/10351 From now on we use ENV to customise if needed 2013-12-18 00:46:37 -05:00			`host_names:`
clean up config to use global settings 2013-12-19 23:12:23 -05:00			`- <%= GlobalSetting.hostname %>`