2026/10/11reading time+ 3 min

PostgreSQL Configuration

Warning

monetr is migrating from using this configuration to a new config layout, this configuration will continue to work for the next few releases but will eventually stop working and require configuration files to be updated. If you are configuring your server via environment variables you should be fine.

See Database Configuration for more details.

monetr's primary database is PostgreSQL and is required in order for monetr to run. monetr also uses PostgreSQL as a basic pub-sub system via LISTEN and NOTIFY commands.

Officially monetr supports PostgreSQL version 16 and higher.

config.yaml

postgresql:
  address: "localhost"
  port: 5432
  username: "monetr"
  password: "..."
  database: "monetr"
  tls: false
  insecureSkipVerify: false
  caCertificatePath: "</tls/ca.cert>"
  keyPath: "</tls/tls.key>"
  certificatePath: "</tls/tls.cert>"

Name	Type	Default	Description
`address`	String	`localhost`	The IP, or DNS resolvable address of your PostgreSQL database server.
`port`	Number	`5432`	Port that the PostgreSQL server can be reached at.
`username`	String	`postgres`	Username that monetr should use to authenticate the PostgreSQL server.
`password`	String		Password that monetr should use to authenticate the PostgreSQL server.
`database`	String	`postgres`	Database that monetr should use, monetr may attempt to run migrations on startup. The user monetr is using should have permissions to create tables and extensions.
`tls`	Boolean	`false`	If true then monetr will connect to PostgreSQL using TLS. TLS is also used if any of the certificate paths below are provided.
`insecureSkipVerify`	Boolean	`false`	If you are using TLS with PostgreSQL but are not distributing a certificate authority file, then you may need to skip TLS verification.
`caCertificatePath`	String		Path to the certificate authority certificate file. If you are verifying your TLS connection then this is required or the server certificate must be among the hosts certificate authorities already.
`keyPath`	String		Path to the client TLS key that monetr should use to connect to the PostgreSQL server.
`certificatePath`	String		Path to the client TLS certificate that monetr should use to connect to the PostgreSQL server.
`migrate`	Boolean	`true`	Automatically apply database migrations on startup.

Info

monetr watches the certificate files for changes, so certificates can be rotated without restarting the server. New connections to PostgreSQL will use the new certificates right away, and existing connections are replaced with new ones within a few minutes.

The following environment variables map to the following configuration file fields. Each field is documented below.

Variable	Config File Field
`MONETR_PG_ADDRESS`	`postgresql.address`
`MONETR_PG_PORT`	`postgresql.port`
`MONETR_PG_USERNAME`	`postgresql.username`
`MONETR_PG_PASSWORD`	`postgresql.password`
`MONETR_PG_DATABASE`	`postgresql.database`
`MONETR_PG_TLS`	`postgresql.tls`
`MONETR_PG_INSECURE_SKIP_VERIFY`	`postgresql.insecureSkipVerify`
`MONETR_PG_CA_PATH`	`postgresql.caCertificatePath`
`MONETR_PG_KEY_PATH`	`postgresql.keyPath`
`MONETR_PG_CERT_PATH`	`postgresql.certificatePath`

Database Migrations

The provided Docker Compose file will automatically run database migrations on startup as needed. However if you want to run the migrations manually you can remove the --migrate flag from the serve command in the compose file.

To run database migrations manually run the following command:

Run Database Migrations

monetr database migrate

To see the current database schema version run the following command:

Database Schema Version

monetr database version

#PostgreSQL Configuration

#Database Migrations

PostgreSQL Configuration

Database Migrations