5163a8fcb9
On GitLab Cloud, MySQL connection reaping seemed to cause more problems (exceptions and segfaults in the native MySQL client) than it solved.
39 lines
784 B
YAML
39 lines
784 B
YAML
#
|
|
# PRODUCTION
|
|
#
|
|
production:
|
|
adapter: mysql2
|
|
encoding: utf8
|
|
reconnect: false
|
|
database: gitlabhq_production
|
|
pool: 10
|
|
username: git
|
|
password: "secure password"
|
|
# host: localhost
|
|
# socket: /tmp/mysql.sock
|
|
|
|
#
|
|
# Development specific
|
|
#
|
|
development:
|
|
adapter: mysql2
|
|
encoding: utf8
|
|
reconnect: false
|
|
database: gitlabhq_development
|
|
pool: 5
|
|
username: root
|
|
password: "secure password"
|
|
# socket: /tmp/mysql.sock
|
|
|
|
# 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: &test
|
|
adapter: mysql2
|
|
encoding: utf8
|
|
reconnect: false
|
|
database: gitlabhq_test
|
|
pool: 5
|
|
username: root
|
|
password:
|
|
# socket: /tmp/mysql.sock
|