Quarto#
Quarto is an open-source scientific and technical publishing system built on Pandoc.
Content authored using Quarto can be published to RStudio Connect.
Important
Quarto development is active and ongoing. RStudio Connect includes preview support for Quarto content. Please let your Customer Success representative know about your experience using Quarto with Connect.
Installing Quarto#
Quarto must be installed on your system before configuring RStudio Connect to allow support for Quarto content. Follow RStudio's Quarto Installation instructions when installing Quarto.
Enabling Quarto Support#
If you used the Quarto Debian installer, Quarto will be available at
/usr/local/bin/quarto
. Configure RStudio Connect to use this default location:
; /etc/rstudio-connect/rstudio-connect.gcfg
[Quarto]
Enabled = true
Executable = "/usr/local/bin/quarto"
If you installed using the Quarto .tar.gz
or another method, you may have
installed Quarto elsewhere. You can support multiple Quarto versions in this
way, providing an Executable
for each:
; /etc/rstudio-connect/rstudio-connect.gcfg
[Quarto]
Enabled = true
Executable = "/opt/quarto/1.0.0/bin/quarto"
Executable = "/opt/quarto/0.9.498/bin/quarto"
Executable = "/opt/quarto/0.9.344/bin/quarto"
Note
Changing any of the Quarto configuration settings requires a restart of RStudio Connect.
Quarto support is only available when the
Quarto.Enabled
is enabled and
the Quarto.Executable
setting references a valid Quarto installation. RStudio Connect will warn at
startup if Quarto is enabled without specifying an installation. Connect fails
to start if Quarto is enabled but references an invalid installation.
A compatible version of Quarto is identified when content is deployed. That Quarto installation is used any time Quarto is needed for that content.
Quarto content may contain R and Python code chunks; when that content is deployed, compatible versions of R and Python are identified and used with Quarto anytime that content is run. Quarto support does not require either R or Python installations, but content that uses R or Python will succeed only if a compatible installation is available.
Quarto Version Matching#
RStudio Connect attempts to find a Quarto installation that is appropriate for your content. By default, it applies a "nearest" matching approach. This algorithm attempts to always find a version of Quarto to use with your content. More deployments will succeed, but not always with the same version of Quarto that is used by the author.
If you would prefer a strict association between authored and deployed Quarto versions, you can choose to use an "exact" matching approach.
The "nearest" matching algorithm is the most flexible option and favors publication of your content over precise duplication of the authoring environment.
The "major-minor" algorithm is a middle ground between "nearest" and "exact".
It requires exact MAJOR.MINOR
matching but is flexible about the patch
level. This is a useful option when your desktop and server may occasionally
have different update cycles when installing bug fix releases.
An inconsistent version of Quarto occasionally causes problems when installing package dependencies. For the best results, make sure that RStudio Connect has access to the same versions of Quarto used to author content.
The Quarto version matching approach is controlled with the
Quarto.VersionMatching
configuration setting.
- nearest
-
Find an installation that is close to the version used when authoring the content. This algorithm uses the ordered tests when looking for
MAJOR.MINOR.PATCH
version matches:-
Use exact version match.
-
If there are matching
MAJOR.MINOR
releases, use least-greater version. -
If there are matching
MAJOR.MINOR
releases, use latest of these. -
Use least-greater version across all releases.
-
Use latest across all releases.
-
- major-minor
-
Find an installation with an exact
MAJOR.MINOR
version match that is close to the version used when authoring the content. If a compatible version cannot be found, content will fail to deploy. The algorithm is a constrained "nearest" search:-
Use exact version match.
-
If there are matching
MAJOR.MINOR
releases, use least-greater version. -
If there are matching
MAJOR.MINOR
releases, use latest of these.
-
- exact
-
Finds an installation that exactly matches the version used when authoring the content. If a matching version cannot be found, content will fail to deploy.