Publish Quarto Documents — quarto_publish

Publish Quarto documents to Posit Connect, ShinyApps, and RPubs

Usage

quarto_publish_doc(
  input,
  name = NULL,
  title = NULL,
  server = NULL,
  account = NULL,
  render = c("local", "server", "none"),
  metadata = list(),
  ...
)

quarto_publish_app(
  input = getwd(),
  name = NULL,
  title = NULL,
  server = NULL,
  account = NULL,
  render = c("local", "server", "none"),
  metadata = list(),
  ...
)

quarto_publish_site(
  input = getwd(),
  name = NULL,
  title = NULL,
  server = NULL,
  account = NULL,
  render = c("local", "server", "none"),
  metadata = list(),
  ...
)

Arguments

input: The input file or project directory to be published. Defaults to the current working directory.
name: Name for publishing (names must be unique within an account). Defaults to the name of the input.
title: Free-form descriptive title of application. Optional; if supplied, will often be displayed in favor of the name. When deploying a new document, you may supply only the title to receive an auto-generated name
server: Server name. Required only if you use the same account name on multiple servers.
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).
render: local to render locally before publishing; server to render on the server; none to use whatever rendered content currently exists locally. (defaults to local)
metadata: Additional metadata fields to save with the deployment record. These fields will be returned on subsequent calls to deployments().
...: Named parameters to pass along to rsconnect::deployApp()

Examples

if (FALSE) { # \dontrun{
library(quarto)
quarto_publish_doc("mydoc.qmd")
quarto_publish_app(server = "shinyapps.io")
quarto_publish_site(server = "rstudioconnect.example.com")
} # }