rsconnect 1.0.2
-
Fixed redeployments to shinyapps.io where
appName
is provided, but no local
record of the deployment exists. (#932) -
deployApp()
andwriteManifest()
now error if your library andrenv.lock
are out-of-sync. Previously it always used what was defined in therenv.lock
but that was (a) slow and (b) could lead to different results than what you
see when running locally (#930). -
Deploying from an renv project includes the
renv.lock
in the bundle. A
manifest created for an renv project references therenv.lock
in the
manifest.json
. (#926) -
Use the environment variable
RSCONNECT_PACKRAT
to analyze dependencies
using packrat, as was done prior to rsconnect-1.0.0. Use of the
rsconnect.packrat
option is discouraged, as it is not effective when using
push-button deployment in the RStudio IDE. (#935) -
The
renv.lock
is ignored when theRSCONNECT_PACKRAT
environment variable
or thersconnect.packrat
option is set. (#936) -
The content type is inferred by analyzing the set of top-level files. (#942)
-
deployApp()
andwriteManifest()
accept an optionalappMode
argument.
Provide this argument if your project includes auxiliary files which mislead
the existingappMode
inference. For example, if an HTML project includes
a downloadable Shinyapp.R
, that content will be assumed to be a Shiny
application even if that application is not meant to be run. (#948) -
appDependencies()
accepts anappFileManifest
argument as an alternate
way of providing the target set of files.