Ignore Custom CRAN Mirror
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 409
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
When rsconnect running on RStudio Cloud generates a packrat lock file, it captures our custom internal CRAN mirror/proxy that is set via RProfile.site:
PackratFormat: 1.4
PackratVersion: 0.4.8.1
RVersion: 3.4.0
Repos: CRAN=http://package-proxy
This is problematic when deploying to RSC outside the RStudio Cloud environment, since that internal proxy is not available.
Any ideas for a workaround, perhaps by disabling the capture of the custom CRAN repo?
Contributor guide
No contributing guide indexed for this repository
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 by tracing how packrat generates its lock file and captures the CRAN repository configured through RProfile.site. Reproduce the RStudio Cloud case with a custom internal mirror, then verify that deployment outside that environment no longer records an unavailable mirror; the issue does not name a specific test file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100