Feature/41 renv rsconnect updates

[GuidoMaggio]

Update of renv chapter. See also #41

• added a phrase about snapshot.type = "explicit" / "implicit"
• updated what is generated in the "renv" folder
• Mentioned in an additional sentence the PPM repo
• options(repos = "https://packagemanager.rstudio.com/cran/2023-01-02") works to fix the date of the repo, like MRAN was working previously. tested.
• added a second sentence about renv::snapshot(dev = TRUE)
• rephrased/improved "Caching the packages' versions", adding new insight from the help file of renv::status
• Added few lines and examples about renv::checkout()

I have tested the usage of renv::checkout(date = , repos = ) and options(repo = ). Also checkout is then setting the new repo to the date specified (or to the repos url).
I.e. renv::checkout(date = "2023-01-01" ) would then set also options(repos = "https://packagemanager.rstudio.com/cran/2023-01-01").

Checkout has more options, packages can be installed, or only a snapshot of the renv.lock can be done.

Update of CI-CD chapter.

• updated workflows yml to mirror ShinyCICD repo
• added forceUpdate = TRUE to rsconnect::deployApp

[riccardoporreca]

@GuidoMaggio, the workflows are no fully up-to-date with ShinyCICD

When porting updates done and tested in ShinyCICD to the techguides, I would always try to get in ShinyCICD the workflows from the techguides to verify we have full consistency, via

usethis::use_github_file("miraisolutions/techguides", ref="feature/41-renv-rsconnect-updates",path="shiny-ci-cd/actions/ci-cd.yml", save_as = "shiny-ci-cd/actions/ci-cd.yml")
usethis::use_github_file("miraisolutions/techguides", ref="feature/41-renv-rsconnect-updates",path="shiny-ci-cd/actions/ci-cd-renv.yml", save_as = "shiny-ci-cd/actions/ci-cd-renv.yml")

Also deploy-shinyapps.io lacks some of the refinements we did in ShinyCICD
(NOTE: we cannot use usethis::use_github_action(), as we have in the techguides for a branch that contains "/").

[GuidoMaggio]

@riccardoporreca I have added 'renv' instead of 'release' in the -renv.yml. Here I did not spot other differences with ShinyCICD.
As for the deploy script, I added the appFiles argument.

usethis::use_github_file("miraisolutions/techguides", ref="feature/41-renv-rsconnect-updates",path="shiny-ci-cd/actions/ci-cd.yml", save_as = "shiny-ci-cd/actions/ci-cd.yml")
usethis::use_github_file("miraisolutions/techguides", ref="feature/41-renv-rsconnect-updates",path="shiny-ci-cd/actions/ci-cd-renv.yml", save_as = "shiny-ci-cd/actions/ci-cd-renv.yml")

The code above works well to me

[riccardoporreca]

Here I did not spot other differences with ShinyCICD.
As for the deploy script, I added the appFiles argument.

There is more in both cases that we want to have. Maybe it is easier for me to take over, since some of the changes should probably be explained in the techguides as part of this content refresh. @GuidoMaggio let's coordinate on this.

Btw, in the past I actually pulled in the full files from ShinyCICD to avoid manual pasting and have more traceability, see 24798ad

=> UPDATE: I have started to commit the complete workflow files, see c8fde8b

[riccardoporreca]

@GuidoMaggio, I have pushed my updates and general review of the Shiny CI/CD chapter.

I plan to do the same for the renv chapter

[riccardoporreca]

@GuidoMaggio, @RolandASc, I ended up doing a major review and partial re-write/restructuring of the renv chapter, which I just pushed.

[riccardoporreca]

@GuidoMaggio, this is complete from my side, please cross-review the changes I did

Followed-up directly by committing to the branch

[GuidoMaggio]

2 changes requested