Deploying Streamlit in ShinyProxy platform

ShinyProxy is a deployment platform built for #rstats Shiny, and extendable to other apps, including Streamlit :slightly_smiling_face:

This Github repo provides a minimal example.

Why ShinyProxy?

  • single platform capable of hosting various apps (e.g., Streamlit, Flask, Dash, Shiny)
  • open-source platform
  • built-in authentication, with user-friendly configuration for users with minimal admin background
  • managed containers for scaling up
  • supportive community, like Streamlit :raised_hands:

Hey @leungi, welcome to the Streamlit community! Thanks for dropping by to share this with us.

Did you experience any downsides deploying this way? Not implying there should be, just wondering.


@randyzwitch: thanks again to your team for #streamlit!

The only downside is that users need to know a bit of #docker #containers.

I believe having an official #streamlit #docker hub entry :star_struck: will be very useful, especially when apps being built get more complex (e.g., read for a containerized database, and write to a shared volume).

1 Like

Thanks for the suggestion! I think this is an area we’ll be able to get to eventually, as we see how users start building complex apps as you say. Meaning, if everyone starts build apps with Postgres or SQLite, then we’ll have a way to proceed. Right now, it’s not clear to me there is one set of tools that everyone uses, besides what are already Streamlit dependencies.