[1] [CITE@en[Engine Configuration — SQLAlchemy 0.7 Documentation]]
( ([TIME[2012-10-28 05:05:12 +09:00]] 版))
<http://docs.sqlalchemy.org/en/rel_0_7/core/engines.html#database-urls>

[2] [CITE@en[PostgreSQL: Documentation: 9.2: Database Connection Control Functions]]
( ([TIME[2014-10-18 03:23:31 +09:00]] 版))
<http://www.postgresql.org/docs/9.2/static/libpq-connect.html#LIBPQ-CONNSTRING>

[3] [CITE@en[PostgreSQL: Documentation: 9.5: Database Connection Control Functions]]
([TIME[2016-06-24 10:21:00 +09:00]])
<https://www.postgresql.org/docs/current/static/libpq-connect.html#AEN42532>

[4] [CITE@en['/' is not allowed in domains · Issue #26 · servo/rust-url]]
([TIME[2016-06-24 10:25:19 +09:00]])
<https://github.com/servo/rust-url/issues/26>

[FIG(quote)[
[FIGCAPTION[
[5] [CITE@en[Heroku Postgres | Heroku Dev Center]]
([TIME[2016-11-17 22:54:11 +09:00]])
<https://devcenter.heroku.com/articles/heroku-postgresql>
]FIGCAPTION]

> Once Heroku Postgres has been added a DATABASE_URL or HEROKU_POSTGRESQL_COLOR_URL setting will be available in the app configuration and will contain the URL used to access the newly provisioned Heroku Postgres service. DATABASE_URL will be given to the database if it is the first one for the application, otherwise the HEROKU_POSTGRESQL_COLOR_URL will be created. This can be confirmed using the heroku config command.
> $ heroku config -s | grep HEROKU_POSTGRESQL
> HEROKU_POSTGRESQL_RED_URL=postgres://user3123:passkja83kd8@ec2-117-21-174-214.compute-1.amazonaws.com:6212/db982398
> 

]FIG]


[FIG(quote)[
[FIGCAPTION[
[6] [CITE@en[Configuring Rails Applications — Ruby on Rails Guides]]
([TIME[2016-10-29 12:23:50 +09:00]])
<http://edgeguides.rubyonrails.org/configuring.html>
]FIGCAPTION]

> This same information can be stored in a URL and provided via an environment variable like this:
> > puts ENV'''[''''DATABASE_URL'''']'''
> postgresql://localhost/blog_development?pool=5
> 

]FIG]


[FIG(quote)[
[FIGCAPTION[
[7] [CITE[The DB-URI — TurboGears 1.0 documentation]]
([TIME[2013-01-12 16:52:59 +09:00]])
<http://turbogears.org/1.0/docs/DbUri.html>
]FIGCAPTION]

> If your Linux or OS X installation has a standard setup and there’s a live socket at /tmp/.s.PGSQL.5432, your SQLAlchemy PostgreSQL dburi can be this simple:
> postgres:///dbname
> To specify the socket file for PostgreSQL, put the absolute path after the double slash:
> postgres:///var/run/postgresql/test?debug=1
> However, there are bugs in the DSN parser for SQLObject, so that it fails to separate the socket path from the database name. A DSN like this works around that issue:
> postgres:///dbname?host=/path/to/socket

]FIG]