Usage
deployApp(appDir = getwd(), appFiles = NULL, appPrimaryDoc = NULL, appSourceDoc = NULL, appName = NULL, contentCategory = NULL, account = NULL, server = NULL, upload = TRUE, launch.browser = getOption("shinyapps.launch.browser", interactive()), quiet = FALSE, lint = TRUE, metadata = list(), ...)
Arguments
appDir
Directory containing application. Defaults to current working
directory.
appFiles
The files to bundle and deploy (only if upload =
TRUE
). Can be NULL
, in which case all the files in the directory
containing the application are bundled.
appPrimaryDoc
If the application contains more than one document, this
parameter indicates the primary one, as a path relative to appDir
.
Can be NULL
, in which case the primary document is inferred from the
contents being deployed.
appSourceDoc
If the application is composed of static files (e.g
HTML), this parameter indicates the source document, if any, as a fully
qualified path. Deployment information returned by
deployments
is associated with the source document. appName
Name of application (names must be unique within an
account). Defaults to the base name of the specified appDir
.
contentCategory
Optional; the kind of content being deployed (e.g.
"plot"
, "document"
, or "application"
).
account
Account to deploy application to. This
parameter is only required for the initial deployment of an application
when there are multiple accounts configured on the system (see
accounts). server
Server name. Required only if you use the same account name on
multiple servers.
upload
If TRUE
(the default) then the application is uploaded
from the local system prior to deployment. If FALSE
then it is
re-deployed using the last version that was uploaded.
launch.browser
If true, the system's default web browser will be
launched automatically after the app is started. Defaults to TRUE
in
interactive sessions only.
quiet
Request that no status information be printed to the console
during the deployment.
lint
Lint the project before initiating deployment, to identify
potentially problematic code?
metadata
Additional metadata fields to save with the deployment
record. These fields will be returned on subsequent calls to
deployments
.