I am trying to save resources by deploying from a vm which iv added multiple nic’s to
If my understanding is correct I should be able to declare a ip I want streamlit to broadcast from and set that in my app
When I do this, the same app is deployed to both ips.
Is my understanding incorrect or am I doing something wrong?
My main issue is that I run out of available ports quickly for my apps.
HI @andrew06074, welcome to the Streamlit community!
I’m slightly confused about your approach here. If you add two NICs, wouldn’t that create two separate networks?
If you want to run two different apps on different ports, you should be able to do it on the same network, by passing the port as a command-line parameter:
https://docs.streamlit.io/en/stable/streamlit_configuration.html#set-configuration-options
Best,
Randy
Hey Randy, thanks for the reply
It looks like streamlit uses the the ip of my client to create the server and broadcast
By adding the additional NIC to my VM im hoping my client receives another address to boradcast from.
My issue is that I run out of available port on my vm rather quickly, im currently using 443,80 and 8501 but as indicated that only allows me 3 apps.
Those ports are just conventions though, you can broadcast on any port you’d like. Or is that restricted on your network?
The are restricted on my domain however I have the ability to open them on my client where streamlit lives
What do you mean they are for convention? Streamlit requires http requests to run no? If that is not the case do you know if there is documentation of compatible ports?
There are ports that are generally considered “well-known”, such as this list:
But if you wanted to broadcast a lot of Streamlit apps, you should have no problem doing 8501, 8502, 8503 and so on until you run out of apps.
Best,
Randy
Ill give it a try, much appreciated!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
These cookies are necessary for the website to function and cannot be switched off. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us understand how visitors move around the site and which pages are most frequently visited.
These cookies are used to record your choices and settings, maintain your preferences over time and recognize you when you return to our website. These cookies help us to personalize our content for you and remember your preferences.
These cookies may be deployed to our site by our advertising partners to build a profile of your interest and provide you with content that is relevant to you, including showing you relevant ads on other websites.