Deploy to github
When creating an opensaas project, should i deploy every folder separately with their own repository? Or just one repo that regroup them all?
5 Replies
Hi @pipas. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Wohooo @pipas, you just became a Waspeteer level 1!
----------------------
Based on the knowledge sources provided, I can offer some guidance on deploying an OpenSaaS project, though the information is not specifically about GitHub deployment. Here's what we can infer:
1. The OpenSaaS template consists of two main parts: the SaaS application and the blog/documentation.
2. For deployment, it's recommended to deploy these parts separately:
- The SaaS portion is typically deployed to a platform like Fly.io
- The static blog/docs portion is recommended to be deployed to a platform like Netlify
OpenSaaS Deployment Guide mentions these deployment strategies, though it may need updating with more specific information.
3. Regarding repository structure, while there's no explicit mention of how to organize the GitHub repository, the separation in deployment suggests that you could potentially have separate repositories for the SaaS application and the blog/docs.
However, it's important to note that the knowledge sources don't provide a definitive answer about the ideal GitHub repository structure for an OpenSaaS project. The decision to use a single repository or multiple repositories might depend on your specific needs, team structure, and deployment workflow.
If you need more specific guidance on GitHub repository organization for OpenSaaS, you might want to consult the OpenSaaS documentation or reach out to the Wasp community for best practices.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @pipas, 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 meant in github
the app, blog, e2test
1 repo or differents repos for each of them?
I'd say - it's up to you if you want to keep everything in one repo (it's often called monorepo) or if you want to have a repo per each "app". We are used to using monorepos for Wasp and I believe @Vinny (@Wasp) and many other @Wasp Expert use a monorepo for their Open Saas apps