The README file and pkgdown content usually contain all the information needed about how to use a package/shiny app as a User. But what if you want to take a look/contribute to something as a Developer? Is there a preferred way to provide this info? I find this to be a big challenge and would like to let future developers know what needs to be done so they can quickly get to work. I constantly have difficulty trying to figure out what needs to be done:
- for packages, do I use renv::restore or devtools:install_dev_deps or.. ? And what OS packages do I need to install and how (e.g.
sudo apt install qpdf
)? - for a bookdown application (e.g. GitHub - hadley/adv-r: Advanced R: a book) which is not in a package structure, what do I need to install (OS packages and R packages) and how to best do so, in order to be able to render the book?
- for Shiny apps: if not in a package structure, how best to install OS and R packages and successfully kick off the app within Posit Workbench?
I guess I am asking two questions:
- best way to let future developers know what is needed to get my package/shiny app/bookdown set up for Workbench?
- best way to figure out what to do with packages/shiny apps/bookdown, created by others, in order to get them set up in Workbench?
Thanks for any info. My current process when attempting to get Workbench set up when attempting to use packages/apps/bookdowns is to run, get an error related to OS/R packages, install, run again, repeat multiple times until I can finally get it successfully run. I am hoping this is a giant beginner mistake and that I have missed a Chapter 0 which would answer everything.