It contains the connection string for the bound database in the following format:

protocol://username:password@host:port/database_name

db_url

PostgreSQL: postgres://, pgsql://, psql:// or postgresql://

PostGIS: postgis://

MySQL: mysql:// or mysql2://

MySQL for GeoDjango: mysqlgis://

SQLITE: sqlite://

SQLITE with SPATIALITE for GeoDjango: spatialite://

LDAP: ldap://

cache_url

Database: dbcache://

Dummy: dummycache://

File: filecache://

Memory: locmemcache://

Memcached: memcache://

Python memory: pymemcache://

Redis: rediscache://

search_url

ElasticSearch: elasticsearch://

Solr: solr://

Whoosh: whoosh://

Xapian: xapian://

Simple cache: simple://

email_url

SMTP: smtp://

SMTP+SSL: smtp+ssl://

SMTP+TLS: smtp+tls://

Console mail: consolemail://

File mail: filemail://

LocMem mail: memorymail://

Dummy mail: dummymail://

Second is that we’ve added support for database URLs in database.yml, and that we by default will be referring to ENV-backed URLs in the generated files.

DATABASE_URL string The database URL; is of the form: postgresql://localhost/blog_development

The recommended way of specifying your database connection information is to set the DATABASE_URL environment variable. This variable only holds connection information (adapter, database, username, password, host and port), but not behavior information (encoding, pool). If you don't want to use DATABASE_URL and/or want to set database behavior information, you will have to either:

copy our template file: cp config/database.yml.env config/database.yml, or

set a value for some GITLAB_DATABASE_XXX variables

To connect to a database through PEAR::DB, you have to create a valid DSN - data source name. This DSN consists in the following parts:

phptype: Database backend used in PHP (i.e. mysql , odbc etc.)

dbsyntax: Database used with regards to SQL syntax etc. When using ODBC as the phptype, set this to the DBMS type the ODBC driver is connecting to. Examples: access, db2, mssql, navision, solid, etc.

protocol: Communication protocol to use ( i.e. tcp, unix etc.)

hostspec: Host specification (hostname[:port])

database: Database to use on the DBMS server

username: User name for login

password: Password for login

proto_opts: Maybe used with protocol

option: Additional connection options in URI query string format. options get separated by &

The format of the supplied DSN is in its fullest form:

phptype(dbsyntax)://username:password@protocol+hostspec/database?option=value

Most variations are allowed:

phptype://username:password@protocol+hostspec:110//usr/db_file.db

phptype://username:password@hostspec/database

phptype://username:password@hostspec

phptype://username@hostspec

phptype://hostspec/database

phptype://hostspec

phptype:///database

phptype:///database?option=value&anotheroption=anothervalue

phptype(dbsyntax)

phptype

The currently supported database backends are:

dbase -> dBase

fbsql -> FrontBase (functional since DB 1.7.0)

ibase -> InterBase (functional since DB 1.7.0)

ifx -> Informix

msql -> Mini SQL (functional since DB 1.7.0)

mssql -> Microsoft SQL Server (NOT for Sybase. Compile PHP --with-mssql)

mysql -> MySQL (for MySQL <= 4.0)

mysqli -> MySQL (for MySQL >= 4.1) (requires PHP 5) (since DB 1.6.3)

oci8 -> Oracle 7/8/9

odbc -> ODBC (Open Database Connectivity)

pgsql -> PostgreSQL

sqlite -> SQLite

sybase -> Sybase

With an up-to-date version of DB, you can use a second DSN format

phptype(syntax)://user:pass@protocol(proto_opts)/database

The Data Source Name has a common format, like e.g. PEAR DB uses it, but without type-prefix (optional parts marked by squared brackets):

[username[:password]@][protocol[(address)]]/dbname[?param1=value1&...&paramN=valueN]

A DSN in its fullest form:

username:password@protocol(address)/dbname?param=value

postgres://username@hostname/databasename

mysql://username:password@hostname:port/databasename

sqlite://path/to/file

postgres:///var/run/postgresql/test?debug=1

mysql://localhost/database?unix_socket=/var/lib/mysql/socket