Skip to content

Documentation #678 #743

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.

Sign up for GitHub

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

Open
pcliquet wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Documentation #678 #743

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 13 additions & 0 deletions charts/rstudio-workbench/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,19 @@ Alternatively, license files can be set during `helm install` with the following
--set-file license.file.contents=licenses/rstudio-workbench.lic
```

## Session Management

By default, VSCode and Positron session pods do not have a timeout configured and may run indefinitely. To prevent excessive resource usage, it is recommended to configure the `session-timeout-kill-hours` setting.

This should be configured in the `vscode.conf` and `positron.conf` files. In the Helm chart, you can set this using the `config` value:

```yaml
config:
vscode:
session-timeout-kill-hours: 10
positron:
session-timeout-kill-hours: 10

## Database

Workbench requires a PostgreSQL database when running in Kubernetes. You must configure a [valid connection URI and a password](https://docs.posit.co/ide/server-pro/database/configuration.html#postgresql) for the product to function correctly. The `database.conf` values may be defined in either `config.database.conf` or `config.secret.database.conf`. The former permits using a `database.conf` file as an existing Kubernetes `Secret`. The latter will automatically create a Kubernetes `Secret` for `database.conf` based on the defined values. In either method of defining database configuration details in the `values.yaml` file, it is possible to include the database password in the configuration section, however, we recommend only adding the connection URI and putting the database password in a Kubernetes `Secret`, which can be [automatically set as an environment variable](#database-password).
Expand Down
Loading