Open aronatkins opened 3 years ago
Hi @aronatkins,
I think this is a duplicate of #1576 which I recently asked @schloerke about. It is currently the way prerendered document are working as it will pre render the app UI before running based on one Rmd (or html) file.
Currently, the document to serve at the root url if not provided (default_file
) is
index.Rmd
or ui.Rmd
(first one found) ORshiny*
runtime. ORindex.html
or ui.html
ORThis logic is the same for both runtime but with prerendered not being able to render according to a new route as with runtime shiny (which render on the run unlike pre rendered). it seems only one Rmd makes sense for shiny prerendered document.
So this is definitly something to look into with the help of the shiny team if we want to support this.
Using rmarkdown 2.6
Given a directory with multiple Rmd containing
runtime: shiny_prerendered
, only one of the documents is served byrmarkdown::run
. This behavior is different than we see with multipleruntime: shiny
documents.First file (named
empty.Rmd
):Only one of the two files is served. In my case, it was always
empty.Rmd
(the alphabetically first file).Both documents can be served if you change
runtime: shiny_prerendered
toruntime: shiny
.The expectations for
rmarkdown::run
(at least forruntime: shiny
documents):http://127.0.0.1:6500/
should serve one of the two applications (based on existingrmarkdown::run
rules).http://127.0.0.1:6500/empty.Rmd
should serve theempty.Rmd
application.http://127.0.0.1:6500/second.Rmd
should serve thesecond.Rmd
application.By filing an issue to this repo, I promise that
xfun::session_info('rmarkdown')
. I have upgraded all my packages to their latest versions (e.g., R, RStudio, and R packages), and also tried the development version:remotes::install_github('rstudio/rmarkdown')
.I understand that my issue may be closed if I don't fulfill my promises.