I am trying to deploy my app that I built of off a fork. I have almost completed the app, however I notice whenever I visit the app it still shows the original template I forked from and not the new version I have created.
This seem like a simple thing that I am overlooking. I’ve read and re-read the streamlit support docs but I can find out what I’m doing wrong?
Hey @raethlein, thank you so much for your help! Much appreciated -
I’m not sure of steps 1 and 2 exactly as you describe them (Apologies this is my first attempt ) - not sure which came first or second.
I would say I started by forking that app from YTQuizzer and begin coding from my forked repo to create wmtsizerizer.
Per your step 4, I’m not sure I redeployed to community cloud from the forked repo, I don’t remember doing that or seeing anything about that.
However, for sure (5) I am currently working on my own forked repo and have it mostly ready but when I click deploy or go visit the live app on community cloud it only displays YTQuizzer?
Maybe I am understanding it wrongly, but if you did not deploy your app to Community Cloud (step 4), how should it be accessible there? When you write “but when I click deploy”, what exactly are you doing there?
Welp, looks like I figured it out just by you asking that question - watched a streamlit video on deployment and fixed it! I created a new app and deployed it directly connected to my repo and it all works fine now!
Thank you so much for this socratic method of solving
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.