You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RStudio has the ability to publish Shiny apps directly to ShinyApps or RStudio Connect (henceforth RSC) from the app. (https://rstudio.com/products/connect/): one click push button Shiny web app deployments.This is the preferred method of deployment for most users.
RSC has a published API that can be implemented by an app. This app will be a HMDC Shiny "middleware" which receives these publish requests but instead of publishing to RSC or ShinyApps publishes to Heroku instead. This will require intercepting the API, these requests, rewriting them, etc.
The RSC middleware I develop, which I will refer to as "shinydrip", can handle these requests.
Helpful Context, Background
How do we test this feature so that we know that it is done?
shinydrip works. This may turn into an epic. Written down essentially to capture my thoughts.
The text was updated successfully, but these errors were encountered:
Story Description
RStudio has the ability to publish Shiny apps directly to ShinyApps or RStudio Connect (henceforth RSC) from the app. (https://rstudio.com/products/connect/): one click push button Shiny web app deployments.This is the preferred method of deployment for most users.
RSC has a published API that can be implemented by an app. This app will be a HMDC Shiny "middleware" which receives these publish requests but instead of publishing to RSC or ShinyApps publishes to Heroku instead. This will require intercepting the API, these requests, rewriting them, etc.
The RSC middleware I develop, which I will refer to as "shinydrip", can handle these requests.
Helpful Context, Background
How do we test this feature so that we know that it is done?
The text was updated successfully, but these errors were encountered: