Streamlit App on subdomain with wasp boilerplate for landing page and backend. possible?
I have my webapp build with streamlit and i'm wondering if I can use wasp boilerplate for the landing page/main website. like the opensaas.sh template website.
I was thinking about running the streamlit app on a subdomain like "app.domain.com" and the landing page just the normal domain like: "domain.com".
I would assume this is all possible because streamlit can be deployed to fly.io and wasp as well so i can run it on the same hosting. but I can't find any topics about this so i'm wondering if I'm missing anything here.
TLDR:
Can i use wasp boilerplate for my streamlit app?
3 Replies
Hi @Hugoo. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the knowledge sources provided, it's not explicitly mentioned how to use Wasp with a Streamlit app. However, Wasp does support custom domains and subdomains, which means you can potentially host your Streamlit app on a subdomain like "app.domain.com" and use Wasp for the main website on "domain.com".
Here's a brief overview of how you could set up a custom domain with Wasp:
1. Add your domain to your Fly client app by running the following command (replace
mycoolapp.com with your domain):
2. Add the DNS records for your domain as instructed by the output of the previous command.
3. Set your domain as the WASP_WEB_CLIENT_URL environment variable for your server app:
After these steps, your app should be available at <https://mycoolapp.com.>
As for using the Wasp boilerplate for your Streamlit app, Wasp is a framework for building web apps with React and Node.js, and it's not clear from the provided sources how it would integrate with a Streamlit app. You might be able to use Wasp for parts of your app (like the landing page), but it's not explicitly stated in the sources how you would do this with a Streamlit app.
For more detailed instructions and information, you might want to check out the Wasp documentation (https://wasp-lang.dev/docs/advanced/deployment/manually) or ask in the Wasp community.
Sources:
- Using a Custom Domain For Your App (https://wasp-lang.dev/docs/advanced/deployment/cli#using-a-custom-domain-for-your-app)
- Deploying Manually (https://wasp-lang.dev/docs/advanced/deployment/manually)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Hugoo, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?I believe you should be able to do this, but I wouldn't use Wasp only for the landing page / main page -> if it is a simple statis content, I bleieve you are better of using sometihng like Astro. Waps is a good fit for more complex apps with client, server and the database.
i'll look into astro thank you!