Summary
rsconnect write-manifest quarto always creates a static document manifest, even for Quarto documents that use server: shiny in their YAML front matter. There's no way to generate a quarto-shiny manifest via the CLI.
Details
The codebase has support for AppModes.SHINY_QUARTO internally, but the CLI doesn't expose this functionality:
- No
--shiny flag on write-manifest quarto
- No auto-detection of
server: shiny in the Quarto document's YAML front matter
write-manifest shiny doesn't recognize .qmd files as valid entry points
Current workarounds
- Use
quarto publish connect instead (which does handle this correctly)
- Manually create a
manifest.json with "appmode": "quarto-shiny"
Expected behavior
Either:
write-manifest quarto should detect server: shiny in the document and create a quarto-shiny manifest automatically, OR- A
--shiny flag should be added to explicitly request a Shiny Quarto manifest
Summary
rsconnect write-manifest quartoalways creates a static document manifest, even for Quarto documents that useserver: shinyin their YAML front matter. There's no way to generate aquarto-shinymanifest via the CLI.Details
The codebase has support for
AppModes.SHINY_QUARTOinternally, but the CLI doesn't expose this functionality:--shinyflag onwrite-manifest quartoserver: shinyin the Quarto document's YAML front matterwrite-manifest shinydoesn't recognize.qmdfiles as valid entry pointsCurrent workarounds
quarto publish connectinstead (which does handle this correctly)manifest.jsonwith"appmode": "quarto-shiny"Expected behavior
Either:
write-manifest quartoshould detectserver: shinyin the document and create aquarto-shinymanifest automatically, OR--shinyflag should be added to explicitly request a Shiny Quarto manifest