-
-
Notifications
You must be signed in to change notification settings - Fork 812
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
Setting Port Number #584
Comments
I run three instances of TGCF on the same machine, each with a different port and using a different Python virtual environment without any issues. TGCF 1 runs on the default Streamlit port, 8501, while TGCF 2 and 3 run on my chosen ports, which i configured by changing the default Streamlit port in the Streamlit configuration. |
Where in the configuration? |
Why do you run 3 instances? Do you use 3 different api_id and api_hash? |
@uwedisch Change the default value to any port of your choice and restart your TGCF @poliandro |
What is about updates when config.py receiving changes because of changed package? Are getting these changes and my changes merged? |
I'm using docker I can't these settings |
Anyone get this to work using docker images? |
i was manage to make it work but now i have built my own because it's more reliable and act more like human |
I'm also using Docker with my own image for two containers. |
Is your feature request related to a problem? Please describe.
When someone has several instances of tgcf running on the same machine the instances grab the next free port, beginning with 8501.
Describe the solution you'd like
I'd like to have the option to set the port number that tgcf binds to.
Describe alternatives you've considered
Starting several instances with one script is not practial. Using Docker for several instances is also not practical because every instance has more than 2 GB data.
Additional context
Running several instances on the same machine is most practial from the point of ressources, but not predictable in relation of the port number a tgcf instance is using.
The text was updated successfully, but these errors were encountered: