@wingly If they’re the same application then I don’t understand why they’re in different repositories to begin with. You’ve already found out the reasons not to do this: it makes coordinating developing features difficult, and makes deployments more difficult.
Preview branch deployments
Hey all, I would like to setup branch preview deployments with forge. Basically when a PR is opened create a new site, database etc and deploy. The QA team can visit this unique url and do the quality assurance. On PR closed delete the site. I don't have a problem to set it up in a Monorepo architecture using forge API or even a package like https://github.com/ryangjchandler/forge-previewer but my situation is a bit more complicated. The frontend application leaves in a separate repository written with Nuxt js and the API is in another repository written with Laravel. I just can't wrap my head around of how to orchestrate this. So let's say a feature of adding an update profile form will need changes in both repositories and probably different people would be working on the tickets. How can I orchestrate the deployment in such cases? Has any one dealt with a similar situation? Any pointers will be greatly appreciated. Thanks
Please or to participate in this conversation.