Merge pull request #758 from pharmaR/ac-673-manifest

Update deployments article to cite manifest file

DESCRIPTION

@@ -1,6 +1,6 @@
 Package: riskassessment
 Title: A web app designed to interface with the `riskmetric` package
-Version: 3.0.0.9016
+Version: 3.0.0.9017
 Authors@R: c( 
     person("Aaron", "Clark", role = c("aut", "cre"), email = "aaron.clark@biogen.com"),
     person("Robert", "Krajcik", role = "aut", email = "robert.krajcik@biogen.com"),

NEWS.md

@@ -16,6 +16,7 @@
 * Updated logo in reports to lighter version to match application UI
 * Utilize `{archive}` to parse DESCRIPTION file in package upload process
 * Incorporates table to show reverse dependencies included in the database
+* updated manifest file and deployments article
 
 # riskassessment 3.0.0
 

dev/run_dev.R

@@ -16,4 +16,3 @@ run_app(pre_auth_user = 'admin')
 # # turn off any options
 # options(shiny.autoload.r=NULL)
 
-

vignettes/Deployment.Rmd

@@ -294,7 +294,7 @@ On Posit Connect, you need to use an absolute path to specify the directory wher
 
 <br>
 
-Beyond that, it's important to note that we strongly encourage those deploying the app to take advantage of the `renv.lock` file used to maintain package version dependencies. For more information on how to use `renv.lock` and our general dev philosophy as it pertains to package management, please read the ["Using `renv`"](https://pharmar.github.io/riskassessment/articles/dev_renv.html) article. Highly related, we encourage the use of git-backed deployment when possible. So, immediately after you update/sync your package dependencies using `renv`, you may want to run `rsconnect::writeManifest()` before deploying from a dedicated branch. For more information on git-backed deployment & manifest files, please read the Posit article on [git-backed content](https://docs.posit.co/connect/user/git-backed/).
+Beyond that, it's important to note that we strongly encourage those deploying the app to take advantage of the `renv.lock` file used to maintain package version dependencies. For more information on how to use `renv.lock` and our general dev philosophy as it pertains to package management, please read the ["Using `renv`"](https://pharmar.github.io/riskassessment/articles/dev_renv.html) article. Highly related, we encourage the use of git-backed deployment when possible. So, immediately after you update/sync your package dependencies using `renv`, you may want to run `rsconnect::writeManifest()` before deploying from a dedicated branch. For convenience, we maintain a current `manifest.json` that should follow the `renv.lock` file in our GitHub repo. So, if you've forked the application, you should be able to deploy the latest version of the app as-is, directly from our `master` branch. For more information on git-backed deployment & manifest files, please read the Posit article on [git-backed content](https://docs.posit.co/connect/user/git-backed/).
 
 <br>