RStudio Server module

[bpmct]

A discussion dedicated to the RStudio Server module. Share your thoughts, questions, and feedback here.

Module Scorecard

Presentation & Onboarding	IDE Integration	Credential Hygiene	Restricted-Environment Readiness	Engineering Quality	Overall
17 / 25	19 / 25	10 / 20	0 / 20	7 / 10	53 / 100

Drilldown

Presentation & Onboarding — 17 / 25

Criterion	Max	Score	Notes
Configuration-mode examples	12	6	README shows one basic example with minimal configuration. No examples demonstrating different modes (e.g., auth enabled vs disabled, different project paths, renv enabled/disabled).
Coder-context framing	8	6	Mentions Coder workspace and shows basic integration, but does not explain what RStudio Server adds on top of Coder or detail where Coder fits in the R development flow.
Visual preview	5	5	README includes an embedded image: 

IDE Integration — 19 / 25

Criterion	Max	Score	Notes
Dashboard entry point	7	7	coder_app resource present with proper configuration (subdomain, icon, URL).
Managed configuration	6	6	Documented support for managed settings via disable_auth, rstudio_user, rstudio_password, enable_renv variables that configure the RStudio environment.
Configurable folder or workdir	6	6	project_path variable documented and implemented, mounts the specified path as the RStudio project directory.
Pre-installed extensions	6	0	Not applicable for RStudio Server; no extension mechanism documented.

Credential Hygiene — 10 / 20

Criterion	Max	Score	Notes
Secrets marked sensitive	16	8	rstudio_user and rstudio_password are marked sensitive = true in main.tf, but README example does not show credential handling (no examples at all for these variables). Defaults are hardcoded as "rstudio"/"rstudio" which are visible in the code.
Non-hardcoded auth path	4	2	disable_auth option exists and defaults to true, providing a path to avoid credentials entirely, but this is not highlighted in README as a security best practice or auth strategy.

Restricted-Environment Readiness — 0 / 20

Criterion	Max	Score	Notes
Mirrorable artifact source	10	0	The Docker image rocker/rstudio:${SERVER_VERSION} is hardcoded in run.sh. No module variable allows overriding the image registry or source. rstudio_server_version only controls the tag, not the image source.
Bring-your-own binary	5	0	No documented way to skip the docker pull or use a pre-existing container/image. The script always pulls the image.
Egress transparency	3	0	No dedicated README section enumerating external endpoints (Docker Hub for rocker/rstudio image, cloud.r-project.org for renv packages). These are only visible in run.sh code.
Runs without sudo	2	0	Script uses docker commands which typically require either sudo or docker group membership (privileged access). No documentation of non-sudo path or rootless docker configuration.

Engineering Quality — 7 / 10

Criterion	Max	Score	Notes
Input quality	6	4	Most inputs have descriptions. share has validation. However, several lack validation (e.g., port could validate range, project_path has no validation). docker_socket description says "(Optional)" but doesn't explain when/why to use it.
Test coverage	4	3	No .tftest.hcl or test files visible in the provided module files. Testing story is unclear. Partial credit for the module being relatively simple and verifiable manually.

Overall — 53 / 100

---

Scored against SCORECARD.md on 2026-07-15 with claude-sonnet-4-5.