I created an multipages app. I try to deploy it on streamlit cloud. I follow the tutorial and i have name my main file ‘Home.py’ (i tried also with ‘Hello.py’). I created a subfolder named ‘pages’ and each page of my app start the name with a number and underscore (1_Analyse.py , 2_Glossaire.py). BUT…
When i deploy, i can see just the main page ‘Home.py’ ! Why and how correct it please ?
in pj, a picture of my folder and files organisation on Vs Code.
I took a look at the documentation and I noticed that to run multipage apps you should run:
streamlit run [entrypoint file]
I think it wasn’t that way last time I looked at it so maybe it is new? In any case, there is no way to specify an entrypoint in streamlit cloud. So how is it supposed to know what the entrypoint is?
Hi Goyo,
Thank you for your answer. I already test with this command line ‘streamlit run Home.py’ name of my main file, the entrypoint file. I read in documentation that we can write Hello or Home.py and after create a file ‘pages’. And then, Streamlit understand that ‘Hello’ or ‘Home.py’ file is the entrypoint file.
You mentioned that it shows “Home” in the deployed app, but it should show “Hello” instead, since that’s the name of the python file. Are you sure you’re deploying from the right repo?
See my fork and deployment. Note that there is a pages directory at the same level than the entry point Hello.py, but they are not in the root of the repository.
Thanks for stopping by! We use cookies to help us understand how you interact with our website.
By clicking “Accept all”, you consent to our use of cookies. For more information, please see our privacy policy.
Cookie settings
Strictly necessary cookies
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.
Performance cookies
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.
Functional cookies
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.
Targeting cookies
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.