title: saving "mocked" mongodb collections in version control
body: <p>I am developing on two machines (switching PC and laptop during the week) and try to find the best way to synchronize a limited amount of dummy data in the mongodbs running on each machine.</p>
  
  <p>My first quick &amp; dirty idea was to track the relevant files, containing the collection data inside of a db folder (inside my project folder) by Git. </p>
  
  <p>I saw for example files named e.g. <em>collection-0-1858325258041703863.wt</em> which seem to contain what i am after. 
  However i am not sure about the rest e.g. <em>index-1-1858325258041703863.wt</em> files, <em>sizestorer.wt</em>, <em>WiredTiger.wt</em> etc..
  <strong>Which are the files i have to track and which are the ones i can ignore?</strong></p>
  
  <p>I am aware that i could create a mock server with only json files and that saving binaries in VC is bad, but still i am curious if this way is possible (Mainly because working with MongoCompass is way easier than editing json files)</p>