Closed dmamira closed 4 years ago
You are right, I don't auto-deploy Next Dapp Apps via Github, and I didn't want to commit the Firebase configurations (which are OK to be inlined and revealed) to any public repo, but If you are auto-deploying via Github, I agree /nd/conf.js
needs to go through Github or any other CI workflow.
Thank you.
On second thought, I actually re-excluded nd/conf.*
#129 because the actual repository nextdapp-cli
is cloning when nextdapp create [project-name]
executes is located at https://github.com/warashibe/next-dapp-bare and this repository (next-dapp) is a showcase of what Next Dapp can do. So next-dapp-bare
repository has been modified to NOT exclude nd/con.*
files, but this repository stays what It used to be without including nd/conf.*
files, so we don't expose anyone's Firebase configurations to be abused.
nd/conf.js is a file that does not contain a private key. So I don't think it's necessary to add it to gitignore. If this is added to gitignore, auto-deploy to vercel won't work.