I am trying to setup a collaborative development environment for make apps in my organization, following this guide.
I setup a git repository and created my 2 apps: the production app app-<id1> and the testing app app-testing-<id2>. <id1> and <id2> are random strings that are generated by make when I create my app, it does not seem I have control over it. When doing so, both app IDs are stored in the origins node in makecomapp.json, which is part of version control.
I shared this repository with my teammate so that he can contribute to the app and test it in his own testing app. This means he will need to create his own app app-testing-<id3>. This is not ideal, because if he wants to deploy his app, he will have to create a new origin, which will in turn be part of version control! I don’t want to have a new origin for each collaborator in my organization.
Actually, I’m not sure if the whole origins section should be part of version control. Maybe it could be an independent file stored in an untracked folder, like the API key. This way each app origin could be defined in its owner’s workspace only, including the production app’s origin. Or you could keep the origins section for retrocompatibility and as a way to version the production app’s origin, and allow an optional additional-origins.json untracked file for testing apps.