We are getting started with Shotgun configuration and would like to store our studio configuration in version control. Our current plan is:
- production version is stored on network drive A
- staging/testing version is stored on network drive B
- we will deploy from B to A using tank
- we will make/test changes locally and push them to B using Git
- so every developer will have access to the production config, the staging config and their own working copies (Git branches)
Assuming this is a sane approach, which files should we definitely be putting into Git, and which should we definitely *not*? For example, I've noticed there are lots of binaries in the install folder. We wouldn't normally put binaries in Git, but if tank doesn't automagically update these on deployment, we probably need to.
We would like developers to be able to switch between all three stages (production, staging, working) via Shotgun Desktop. This suggests that any stage-specific files should not be in version control? Which files are these?