Closed arisgk closed 5 years ago
Thanks for the PR @arisgk! The problem I can see with this PR is that it would be very easy for me (or anyone I work with on the production app) to pull from the repo and overwrite the prod.js file used in production. That file, obviously, is not committed here because it contains keys. Those keys are just client ids and not secrets, so it wouldn't be devastating to have them in the repo (in fact, I think they were accidentally committed once). But in the event that I start storing secrets in this file as well, I don't want to commit it and I don't want it to be overwritten a pull.
I wonder if it's just easier to include the steps to create the prod.js file like you did in the readme?
Right, I thought that because this prod.js
file is gitignored pulling won't override the existing ones. But we can certainly add instructions to the Readme too, closing this PR.
Fixes #67