I've been running a lot of #rstats scripts lately and sometimes I have to move the scripts around, which means installing packages.

There are many options out there, but none of them fits my use case very well.

Here is what I found (a thread) Option 1: use {packrat}, {renv} etc aimed at full reproducibility.

A loosely defined project combined with strict versioning requirements, often erring on the side of more dependencies are safer

Rmarkdown is a reproducible authoring format in #rstats supporting dozens of static and dynamic output formats.

Let's review why and how you should containerize Rmd files! Runtime: shiny - Add this to the document’s YAML header.

Now you can add Shiny widgets and #Shiny render functions to the file’s #rstats code chunks.

Use rmarkdown::run() as CMD in your Dockerfile