If I try to embed the first URL into another website with HTML code, it poses no error and displays correctly.
The code for doing that is the following:
However, if I use the other URL in the src, the page gets the redirected you too many times error (Although the app works properly).
I would appreciate if you could give me some insight about what is different between both URLs, and if there is a way to configure the cloud as to keep getting the previous URL structure.
If the goal is to have a predictable easy to share url, is it possible to keep the previous URL structure?
For example, one could share the link https://share.streamlit.io/postdatacrc/mediciones_qoe/main/Streamlit-Mediciones_QoE.py to always send the user to the latest hosted version of the app.
In about a week, we’re going to be switching Community Cloud to a unique subdomain structure. All apps will share the same basic url structure like above which should help with predictability. Here’s a post explaining more: Coming soon: New subdomain URL format and customizable subdomains!
Hey @tc1 , thank you for your response. I did see the change. However, you can see that there is a “short hash” at the end. Is this based on the hash of the latest commit? If it is, wouldn’t the hash change with each deployment? My usecase is that I want to provide a link to every team member that would always take them to the LATEST deployment of the app from main branch, for example. Thanks
Hi - I have a similar question to @alskdu. I am currently embedding an app within an iframe on my website, and want to confirm that the new subdomain structure won’t require me to update my embed URL each time I push a new change to GitHub (the hash?). Can you confirm?
If the goal is to have a predictable easy to share url, is it possible to keep the previous URL structure?
We are moving away from the previous URL structure to support Custom URLs and also to improve app isolation and security.
However, you can see that there is a “short hash” at the end. Is this based on the hash of the latest commit? If it is, wouldn’t the hash change with each deployment?
The “short hash” is not related in any way to the hash of the latest commit. It is an internal hash used to create a unique subdomain for an app. It prevents collisions with other app subdomains in case they share the same app co-ordinates(repo name, app name, file name etc).
The unique app url is a stable url and does not change with each deployment.
The new url with (streamlitapp.com/?embedded=true) works fine for a desktop version, but doesn’t work at mobile, just blinking screen. Any idea how to fix it? chart
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.