Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support website integration #43

Open
clnsmth opened this issue Jun 23, 2019 · 2 comments
Open

Support website integration #43

clnsmth opened this issue Jun 23, 2019 · 2 comments
Labels
enhancement New feature or request

Comments

@clnsmth
Copy link
Member

clnsmth commented Jun 23, 2019

What would it take to integrate our app into a website? This feature was originally set as a post-production-release enhancement.

@clnsmth clnsmth added the enhancement New feature or request label Jun 23, 2019
@wetlandscapes
Copy link
Collaborator

Here are some common methods for running shiny apps on the web:

The RStudio and DigitalOcean options are appealing, because they are easy to implement (more so the RStudio option). However, that could potentially get expensive as more instances and time on the app generally mean more money. There are academic discounts, however: https://www.rstudio.com/pricing/academic-pricing/. That said, one could spend \$3,000-20,000/year on a shiny stuff. For specific info on hosting from shinyapps.io (\$3,300/year): https://www.shinyapps.io/

A seemingly cheaper option, but one that would require more back-end support from IT, is to use a server-hosted container system (e.g., Kubernetes and Docker) to dynamically spin up instances of R on a server that could host the Shiny app, dependent on demand.

Once the app has initialized its simply spewing out html, css, javascript, etc. That means it could be "placed" into an existing website using an iframe. That is, the web design crew responsible for the website would have to explicitly write in code to include instances of the shiny application via some host server (listed above).

Conclusion:

  • Simplest, but most expensive option is to use RStudio commercial products.
  • Cheapest, but most complicated is using a self-hosted server with containers, which would have to be run by an IT department somewhere.

@CoastalPlainSoils
Copy link
Collaborator

With An's question in another thread about processing large datasets, would both of these options run at the same speed or would one be faster than the other? @wetlandscapes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants