sh file) with one line that had two parts, the absolute filepath to the R binaries on the network drive, and then the. R file and saved it in the app's working directory that had these lines in it to set the working directory and source the global variables.Ĭontents of app_start.R setwd("shared/drive/app_directory")Īll of this was started by a batch file (if windows, otherwise a.
The app that I wrote was saved on that same network drive. So I saved the R binaries to that network drive. I knew that they could access a particular shared network drive. I recently had to deal with the same issue you faced, and wasn't sure how to get some sort of POC in front of the eyes of those who make the decisions. If you are interested in other features, check out FI Labs - RInno Remotes = c("talgalili/installr", "daattali/shinyjs")) Pkgs = c("shiny", "jsonlite", "magrittr", "plotly", "ggplot2"), You can also include GitHub packages to the remotes argument: create_app( It defaults to include shiny, magrittr and jsonlite, so if you are using other packages like ggplot2 or plotly, just add them to the pkgs argument. If you would like to include R for your co-workers who don't have it installed, add include_R = TRUE to create_app: create_app(app_name = "myapp", app_dir = "path/to/myapp", include_R = TRUE) Then you just need to call two functions to create an installation framework: create_app(app_name = "myapp", app_dir = "path/to/myapp") To get started: install.packages("RInno") when a company will not pay for Shiny Server or there are security concerns with cloud services. I just finished developing the RInno package for this exact problem, i.e. I tried it with some co-workers, and it works, but it is more of an office trick than a sustainable solution. Sharing apps over the LAN like this is pretty cool, but it is kind of a hack.
0 kommentar(er)
