Coder powers secure, scalable development across key industries — automotive, finance, government, and technology — enabling faster builds, tighter compliance, and seamless AI adoption in enterprise-grade cloud environments.
For production deployments, we recommend using an external PostgreSQL database (version 13 or higher).
Basic configuration
Before starting the control plane, prepare the database server by creating a role and a database.
Remember that the role must have access to the created database.
With psql:
CREATE ROLE coder LOGIN SUPERUSER PASSWORD 'secret42';
With psql -U coder:
CREATE DATABASE coder;
Coder configuration is defined via environment variables.
The database client requires the connection string provided via the CODER_PG_CONNECTION_URL variable.
The search_path parameter determines the order of schemas in which they are visited while looking for a specific table.
The first schema named in the search path is called the current schema.
By default search_path defines the following schemas:
SHOW search_path;
search_path
--------------
"$user", public
Using the search_path in the connection string corresponds to the following psql command:
ALTER ROLE coder SET search_path = myschema;
Troubleshooting
coder server fails startup with "current_schema: converting NULL to string is unsupported"
Make sure that the schema selected in the connection string ...&search_path=myschema exists and the role has granted permissions to access it.
The schema should be present on this listing: