A common practice is to use a separate file for firebase configurations. For example, only check in a config file firebase.config.ts.example with actual config fields and dummy data. Then during coding time, everyone copy the example file to firebase.config.ts, and fill in their own configurations. This way the code base won't need to store specific config data. Then future CI/CD process can take secret values (e.g. stored in Github account) and fill in those before building and deploying.
(Note: the above approach of config is NOT included in PR #11)
haoyuguo
commented
2 years ago
References:
https://github.com/martcatnip/fireflyWeb/tree/master/src/template
https://www.youtube.com/watch?v=ZrYkNq0qXxs
A common practice is to use a separate file for firebase configurations. For example, only check in a config file
firebase.config.ts.examplewith actual config fields and dummy data. Then during coding time, everyone copy the example file tofirebase.config.ts, and fill in their own configurations. This way the code base won't need to store specific config data. Then future CI/CD process can take secret values (e.g. stored in Github account) and fill in those before building and deploying. (Note: the above approach of config is NOT included in PR #11)