Hi All,
Our company is new to using Retool and wants to explore the possibility of the Source Version control integration in the Retool. We have close to 50-60 screens already built and working in Production, but we do not have SVC yet.
So appreciate this community's help in clarifying the questions we have about this integration.
- We understand we need Retool Enterprise plan to work with the source version control integration.
- Once I have the license and am integrated with Github, can I have all of my screens' code in Github (CSS, JS, SQLs, API calls, or any other resources) so that we can have the changes reviewed as PRs?
- Meaning, in the unforeseen situations, if my Retool server goes down completely, can I still have all the code in Github that I can migrate back to Retool and have the screens up and running on the new server?
- I assume this Github integration allows branch based deployments, is it correct? Because currently each screen seems to have a version, and the developer makes changes on top of it, and marks the same version as "Live" version for it to be available in Production. Can we do branch or tag based deployments to each environment in this scenario?
We would greatly appreciate your inputs on the above, as I mentioned, our company is using Retool for the first time, so wanted to know these details before we acquire enterprise license.
Thanks for your cooperation and understanding.