Sharing is still invitation-only, but today we’re extending 1,000 invites to community members. So if you haven’t signed up yet, sign-up here and we promise to get you an invite as soon as possible.
If you’d like to read a bit more about Streamlit sharing, we recommend taking a look at @Tyler’s tutorial here.
If you need secure deployment, management, and collaboration for your team, then sign-up for Streamlit for Teams (beta will be expanding in late 2020)
Does anyone know whether this also supports scenarios where one has a backend (e.g. FastAPI / Flask) serving the Streamlit app?
In my day job, I find this separation is often needed because the backend eventually gets deployed as a stand-alone microservice. Until now, the way I’ve done this is by dockerizing the backend / frontend and then orchestrating the services with docker-compose.
As far as I can tell, the Streamlit sharing feature operates in a similar manner to binder, so presumably one cannot spawn multiple containers at once … however I would love to be shown otherwise
There’s nothing preventing you from implementing something like this on Streamlit sharing, but at the same time, we haven’t currently built for this sort of scenario. Meaning, it might be possible for you to run Flask from your Streamlit process, but you’ll be competing for resources.
Of course, the containers themselves are connected to the internet, so you can ping other resources as you please. Note that secrets management is being planned, but for the time being, any resources you would be wanting to authenticated against would have the credentials publicly shown.
Secrets management is now available in Streamlit sharing! You need to upgrade to version 0.80 of Streamlit, the temporary documentation location is linked below.
,
