Skip to content
This repository was archived by the owner on Aug 18, 2025. It is now read-only.

chore: document postgres.noPasswordEnv #1131

Merged
merged 2 commits into from
Sep 28, 2022
Merged

chore: document postgres.noPasswordEnv #1131

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
127c8cb
chore: document postgres.noPasswordEnv
johnstcn Sep 28, 2022
ee76b57
fixup! chore: document postgres.noPasswordEnv
johnstcn Sep 28, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions guides/deployments/postgres.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,14 @@ or cluster.
the console, to avoid inadvertently storing credentials in shell history
files.

> Normally, we set the PostgreSQL password as an environment variable in the
> `coderd` deployment with a reference to the Kubernetes secret. If this is
> not desirable, you can instead mount the secret as a file which Coder will
> read at startup. To do this, set the Helm value `postgres.noPasswordEnv` to
> `true`. This will mount the secret under
> `/run/secrets/<.Values.postgres.passwordSecret>/password` and set the
> environment variable `DB_PASSWORD_PATH` for `coderd` to that value.

1. Get the port number for your PostgreSQL instance:

```sql
Expand Down