-
Notifications
You must be signed in to change notification settings - Fork 894
docs: Setup external PostgreSQL server #4901
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,88 @@ | ||
## Recommendation | ||
|
||
For production deployments, we recommend using an external [PostgreSQL](https://www.postgresql.org/) database (version 13 or higher). | ||
|
||
## Basic configuration | ||
|
||
Before starting the Coder server, prepare the database server. Create a role and a database. | ||
Remember that the role must have access to the created database. | ||
|
||
With `psql`: | ||
|
||
```sql | ||
CREATE ROLE coder LOGIN SUPERUSER PASSWORD 'secret42'; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We could consider creating a lower privilege user and granting all on the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Frankly speaking, I would rather keep it simple here. Those, who want to configure the database considering the security requirements can always tweak it :) |
||
``` | ||
|
||
With `psql -U coder`: | ||
|
||
```sql | ||
CREATE DATABASE coder; | ||
``` | ||
|
||
Coder configuration is defined via [environment variables](../admin/configure.md). | ||
The database client requires the connection string provided via the `CODER_PG_CONNECTION_URL` variable. | ||
|
||
```sh | ||
export CODER_PG_CONNECTION_URL="postgres://coder@localhost/coder?password=secret42&sslmode=disable" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I've only seen the URL formatted as There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, these are interchangeable, but I can adjust to the standard pattern There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We seem to actually be using a mixture of both. It might be a good idea for us to standardize behind one usage (see |
||
``` | ||
|
||
## Custom schema | ||
|
||
For installations with elevated security requirements, it's advised to use a separate [schema](https://www.postgresql.org/docs/current/ddl-schemas.html) instead of the public one. | ||
|
||
With `psql -U coder`: | ||
|
||
```sql | ||
CREATE SCHEMA myschema; | ||
``` | ||
|
||
Once the schema is created, you can list all schemas with `\dn`: | ||
|
||
``` | ||
List of schemas | ||
Name | Owner | ||
-----------+---------- | ||
myschema | coder | ||
public | postgres | ||
(2 rows) | ||
``` | ||
|
||
In this case the database client requires the modified connection string: | ||
|
||
```sh | ||
export CODER_PG_CONNECTION_URL="postgres://coder@localhost/coder?password=secret42&sslmode=disable&search_path=myschema" | ||
``` | ||
|
||
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: | ||
|
||
```sql | ||
SHOW search_path; | ||
|
||
search_path | ||
-------------- | ||
"$user", public | ||
``` | ||
|
||
Using the `search_path` in the connection string corresponds to the following `psql` command: | ||
|
||
```sql | ||
SET search_path TO myschema; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not sure if we want to confuse readers, but this would also be an option: ALTER ROLE coder SET search_path = myschema; There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good call, once altered you don't need to set it every time. |
||
``` | ||
|
||
## Troubleshooting | ||
|
||
### Coder server fails startup with "current_schema: converting NULL to string is unsupported" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I ran into this as well when testing it the first time. I love that you added it! ❤️ |
||
|
||
Please 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: | ||
|
||
```sh | ||
psql -U coder -c '\dn' | ||
``` | ||
|
||
## Next steps | ||
|
||
- [Quickstart](../quickstart.md) | ||
- [Configuring Coder](../admin/configure.md) | ||
- [Templates](../templates.md) |
Uh oh!
There was an error while loading. Please reload this page.