chains.json doesn't work nice with version control #47
Description
embark version 0.8.0 now requires the chains.json file to be present in the project root directory. Minimally it contains {}, but will be updated over time to track contract deployments.
Now I don't want this file to be under version control (which would trigger unwanted commits / merge conflicts), so I would put it in .gitignore, but unfortunately embark deploy doesn't generate the file if it is missing (with the minimum {} default content), instead giving the error:
Running "deploy_contracts:development" (deploy_contracts) task
Warning: error reading ./chains.json Use --force to continue.
I can add manual installation instructions for developers, to generate the file, but ideally the file should be generated by default and/or reside outside of the project root directory.