# PostgreSQL. Versions 9.1 and up are supported.
#
# Install the pg driver:
# gem install pg
# On OS X with Homebrew:
# gem install pg -- --with-pg-config=/usr/local/bin/pg_config
# On OS X with MacPorts:
# gem install pg -- --with-pg-config=/opt/local/lib/postgresql84/bin/pg_config
# On Windows:
# gem install pg
# Choose the win32 build.
# Install PostgreSQL and put its /bin directory on your path.
#
# Configure Using Gemfile
# gem 'pg'
#
default: &default
adapter: postgresql
encoding: unicode
# For details on connection pooling, see Rails configuration guide
# http://guides.rubyonrails.org/configuring.html#database-pooling
pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
development:
<<: *default
database: shoutr_development
# The specified database role being used to connect to postgres.
# To create additional roles in postgres see `$ createuser --help`.
# When left blank, postgres will use the default role. This is
# the same name as the operating system user that initialized the database.
#username: shoutr
# The password associated with the postgres role (username).
#password:
# Connect on a TCP socket. Omitted by default since the client uses a
# domain socket that doesn't need configuration. Windows does not have
# domain sockets, so uncomment these lines.
#host: localhost
# The TCP port the server listens on. Defaults to 5432.
# If your server runs on a different port number, change accordingly.
#port: 5432
# Schema search path. The server defaults to $user,public
#schema_search_path: myapp,sharedapp,public
# Minimum log levels, in increasing order:
# debug5, debug4, debug3, debug2, debug1,
# log, notice, warning, error, fatal, and panic
# Defaults to warning.
#min_messages: notice
# 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:
<<: *default
database: shoutr_test
# As with config/secrets.yml, you never want to store sensitive information,
# like your database password, in your source code. If your source code is
# ever seen by anyone, they now have access to your database.
#
# Instead, provide the password as a unix environment variable when you boot
# the app. Read http://guides.rubyonrails.org/configuring.html#configuring-a-database
# for a full rundown on how to provide these environment variables in a
# production deployment.
#
# On Heroku and other platform providers, you may have a full connection URL
# available as an environment variable. For example:
#
# DATABASE_URL="postgres://myuser:mypass@localhost/somedatabase"
#
# You can use this database configuration with:
#
# production:
# url: <%= ENV['DATABASE_URL'] %>
#
production:
<<: *default
database: shoutr_production
username: shoutr
password: <%= ENV['SHOUTR_DATABASE_PASSWORD'] %>
正如您在config/database.yml文件中所看到的，开发和生产环境的密码都没有定义，这些用户也不是在PostgreSQL中创建的，但是我仍然可以推送到Heroku，并且Heroku仍然可以以某种方式提供应用程序利用的PostgreSQL生产环境数据库。
我正在尝试学习 Ruby on rails 开发以及本教程和从 3：50 标记开始，作者做了bundle install并立即做了db:create成功地暗示他可以在开发环境中连接到 PostgreSQL，而无需配置用户并随后更改开发环境config/database.yml中的值，而如果我做同样的结果会导致错误，可以通过在 PostgreSQL 中创建用户并更改 yml 文件中的凭据来解决其中的 couse， 但是，我偶然发现的每个教程都没有显示用户的创建：
/home/webmaster/gems/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:291:in `require'
bin/rails:4:in `<main>'
Caused by:
PG::InsufficientPrivilege: ERROR: permission denied to create database
有两种主要方法可以访问本地 postgresql 数据库。一种是在 database.yml 文件中使用特定的用户/密码组合。另一种是设置本地 postgres 以信任您的用户身份。
对于后一种情况，您需要编辑 pg_hba.conf 文件以具有trust行（允许任何人连接，只需传递用户名）或peer或ident（取决于连接 - 套接字或 tcp - 仅允许与连接用户同名的 postgres 角色，在您的情况下可能webmaster
例如：
# Allow any user on the local system to connect to any database with
# any database user name using Unix-domain sockets (the default for local
# connections).
#
# TYPE DATABASE USER ADDRESS METHOD
local all all trust
# The same using local loopback TCP/IP connections.
#
# TYPE DATABASE USER ADDRESS METHOD
host all all 127.0.0.1/32 trust
您可以在此处找到更多示例：https://www.postgresql.org/docs/devel/auth-pg-hba-conf.html
警告 不要在生产服务器上使用此配置！