Hi Maxime, thanks for your detailed answer!
You’re bang on regarding the setup I was aiming for. I’ve also encountered the merging issue you’re mentioning but was hoping a simple
.gitignore would prevent the
realm_config.json file from being merged. There are some other files I’d like to not merge, like the sync folder (so that the
realmApp_DEV can have Sync’s developer mode ON while the
My reason for wanting to do this is as follows: my app is in production and I want to make a bunch of changes to the schema safely without affecting
realmApp_PROD. So I created the
realmApp_DEV that my client app syncs to when I’m in dev. When I’m ready to push both the new client code and the new realmApp schema to production, I’d like to simply have to do a GitHub merge from dev branch to prod branch and that would automatically bring my schema changes to prod.
So technically, although the deployment to GitHub is bi-directional, I’d only use the functionality in one direction for each environment like so:
realmApp_DEV changes deployed to GitHub dev branch
- GitHub prod branch deployed to
The issue I have is that step 1 doesn’t work (presumably because my GitHub dev branch is not the master branch). Although I’ve read somewhere that it was now possible to deploy to a non-master branch on GitHub.