RSW: instructions for configuring rJava support
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
Following up from a discussion with RStudio support, it would be helpful to have instructions for configuring rJava support in RSW sessions.
This RStudio support article is a good starting point but gets a bit confusing at the end and it is not fully clear if local image modications are needed or which config setting is required, especially when using the helm chart.
Currently it seems that one must configure config.session.r-versions verbatim with the following to get a correct LD_LIBRARY_PATH within the session images:
config:
session:
r-versions: |
Path: /opt/R/4.2.0
Script: /opt/R/4.2.0/lib/R/etc/ldpaths
Path: /opt/R/4.1.3
Script: /opt/R/4.1.3/lib/R/etc/ldpaths
[...]
(credits to Lachlan)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked RStudio support article and the Helm chart's config.session.r-versions setting, including the shown R version paths and ldpaths scripts. Clarify whether local image modifications are needed and document the required Helm configuration for rJava support in RSW sessions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, r
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100