Section 2.7 Hosting Model is missing details about how to correctly deploy applications that have been converted into packages (i.e. the Shiny code is in the R subdirectory). Application loading begins if R is tacked onto the end of the URL, such as, http://shiny.university.edu/applicationAsPackage/R/ (which is unsightly but otherwise there is Page Not Found Error) but it causes problems because commands like load("datasets/experiment.RData") no longer work like they do if load_all() is used at the RStudio command line from the top-level package directory to load the application. Currently, the guide looks like
and it makes no mention of the kind of folder structure described in Chapter 20 of Mastering Shiny book.
Section 2.7 Hosting Model is missing details about how to correctly deploy applications that have been converted into packages (i.e. the Shiny code is in the
R
subdirectory). Application loading begins if R is tacked onto the end of the URL, such as, http://shiny.university.edu/applicationAsPackage/R/ (which is unsightly but otherwise there is Page Not Found Error) but it causes problems because commands likeload("datasets/experiment.RData")
no longer work like they do ifload_all()
is used at the RStudio command line from the top-level package directory to load the application. Currently, the guide looks like and it makes no mention of the kind of folder structure described in Chapter 20 of Mastering Shiny book.