rstudio / environments.rstudio.com Goto Github PK

View Code? Open in Web Editor NEW

7.0 77.0 5.0 8.66 MB

Environment Management for R

Home Page: https://environments.rstudio.com

License: Creative Commons Attribution Share Alike 4.0 International

HTML 82.77% JavaScript 7.53% CSS 5.22% R 4.48%

environments.rstudio.com's People

Contributors

Stargazers

Watchers

Forkers

vergilcw rpln isabella232 lachlansimpson

environments.rstudio.com's Issues

Migrate to RStudio theme

Should the site be moved to blogdown to use RStudio's theme? Can we create an RStudio distill theme that is similar?

Think about how renv will impact RSC (which vendors packrat)

Add content on how to permanently set repos

a la https://support.rstudio.com/hc/en-us/articles/360047157094

Fix link

environments.rstudio.com/reproduce.Rmd

Line 119 in 77effe7

 This scenario is problematic because it encourages [partial upgrades](./reproduce.html#the-big-risk), is often slow, and still results in broken environments! 

I think someone here is responsible for environments.rstudio.com ? on the Strategy Maps page, under the subheader ‘Ticket System’ on the last line the words ‘partial upgrades’ are linked, however, the link actually just takes you back to the same page.

Create outline of Python environment management eco system

Reference

https://pycon.switowski.com/02-packages/

Content ideas

I propose that the following items should be included:

Overview of the ecosystem
Deep dive into poetry (#32):
- usage
- how it works behind the scenes, and what that means to you (high level)
- collaborating with poetry
- publishing content to RStudio Connect
- Choosing package source (pypi, artifactory, rspm)
Deep dive into venv:
- usage
- how it works behind the scenes, and what that means to you (high level)
- collaborating with venv
- publishing content to RStudio Connect
- Choosing package source (pypi, artifactory, rspm)
Deep dive into conda:
- usage
- how it works behind the scenes, and what that means to you (high level)
- collaborating with conda
- publishing content to RStudio Connect that was developed with conda
- Choosing package source (forge vs. anaconda)
comparison of renv:: vs. venv vs. poetry vs. conda workflows (e.g. similar to this https://pandas.pydata.org/pandas-docs/stable/getting_started/comparison/comparison_with_r.html)

The following items should be excluded:

deep dive into pipenv: both third party library that is similar to poetry. It is valid to use over poetry - but would be duplicative of us to go over both.

Add code examples to the upgrade troubleshooting section

Organization

I use this site all the time on demos, and 9/10, I'm mainly looking at the strategy map. I think it should be on the home page -- it's SO GOOD.

How should RSPM work with libraries?

Let me try to flush out two uses cases:

Time traveling
Say you have a project that is no longer running, and you want to try and go back in time. If you just use a frozen repo url, you still have problem because you'll be installing from that old repo into a user library that already has stuff from different points in time. You really need to create a new library first (which we don't offer any affordance for)
Consistent Teams
It is pretty common for orgs to want a majority of users (esp new users) to be using the same sets of packages. Today, an admin could do that by managing a curated repo; but they would still need to either install the packages for users from the curated source, or at a min make sure that after updating the curated repo they somehow get all the users to update their libraries

I think both of these are challenges related to library management

jeff [8:27 AM]
Oh, I see. Yeah I totally agree. That does feel outside of the scope that we originally drew for the product, but I could see why one might argue that it's an incomplete solution without some affordances for that.
You almost want to be able to force updates onto users libraries from RSPM... that doesn't sound like a good idea but maybe there's a way to make it work with a prompt in the IDE or something that informs you that you're behind and lets you opt-in to an update.

Typo in index.Rmd

Line 15, "buisness" should be "business"

TOC?

Ask JJ about ToC support in distill

Rename strategies -> reproduce

Deep dive into poetry

Topics:

usage
how it works behind the scenes, and what that means to you (high level)
collaborating with poetry
publishing content to RStudio Connect
Choosing package source (pypi, artifactory, rspm)

Add video demo of Snapshot and Restore with renv

Proposed addition to `snapshot.Rmd` on line `123`:

### Watch a video demo of Snapshot and Restore with `renv`

<!--html_preserve-->
<html>
<script src="https://fast.wistia.com/embed/medias/sbyf1srsgh.jsonp" async></script><script src="https://fast.wistia.com/assets/external/E-v1.js" async></script><div class="wistia_embed wistia_async_sbyf1srsgh" style="height:360px;position:relative;width:640px"><div class="wistia_swatch" style="height:100%;left:0;opacity:0;overflow:hidden;position:absolute;top:0;transition:opacity 200ms;width:100%;"><img src="https://fast.wistia.com/embed/medias/sbyf1srsgh/swatch" style="filter:blur(5px);height:100%;object-fit:contain;width:100%;" alt="" aria-hidden="true" onload="this.parentNode.style.opacity=1;" /></div></div>
</html>
<!--/html_preserve-->

Review of docs/python/poetry.qmd

@dpastoor can you please review: https://github.com/rstudio/environments.rstudio.com/blob/python-refresh/docs/python/poetry.qmd

A few things to consider when reviewing:

Do the headings and page structure make sense? We should attempt to agree on consistent headings and structure that we can then apply to the conda article, venv article, and renv article.
Do you see anything that is incorrect?
Any ideas on improving the content / narrative?

Rename master to main

In line with other RStudio repos.

Add content on using a frozen snapshot for a single project

Where is R_HOME?

On the R Installation page https://environments.rstudio.com/r-installation - it might also appear elsewhere - there are references to R_HOME that imply the definition of R_HOME is /opt/R/${R_VERSION}/

My understanding from other documentation is that R_HOME is defined by /opt/R/${R_VERSION}/lib/R/ - for example, the support article Managing R with .Rprofile, .Renviron, Rprofile.site, Renviron.site, rsession.conf, and repos.conf notes:

These files are set for each version of R and should be located in R_HOME/etc/. You can findR_HOME by running the command R.home(component = "home") in a session of that version of R. So, for example, if you find that R_HOME is /opt/R/3.6.2/lib/R, the Rprofile.site for R 3.6.2 would go in /opt/R/3.6.2/lib/R/etc/Rprofile.site

Thanks!

Broken link to picking packages

There are a few references on the site to picking.html, which doesn't appear to exist.

See line 137 of reproduce.Rmd and line 175 of repositories.Rmd

audit video content

Update GA with move to posit.co

Hi @kmasiello -

When/if you move this site to environments.posit.co, please update the GA tracking code. All the details are in Confluence!

Thank you!
Sarah

migrate to quarto

must migrate from distill to quarto - below captures notes to the tracking

Typo

Dunno who’s responsible for main page of environments.rstudio.com, which I’m reading through now — generally excellent. I did find a typo that should probably be fixed…under What Makes Up an Environment, bullet that starts “R Packages” has installating, which I like the feel of, but do not believe is a real word…