Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Streamlining project's configuration process #23

Open
hanseaston opened this issue Aug 9, 2020 · 0 comments
Open

Streamlining project's configuration process #23

hanseaston opened this issue Aug 9, 2020 · 0 comments
Labels
backend easy fix! normally can fix in just a few lines of code! enhancement enhancement on an existing feature ideas wanted Need ideas and inputs from others

Comments

@hanseaston
Copy link
Owner

Right now, we have an env file for the backend to store secret keys, while in the frontend code, we have another two js files storing the firebase and stripe connection keys. This setup feels a little cumbersome and it makes the configuration process a little more tedious. There should be a way to streamline the setup the process, for example, maybe storing both the frontend and backend keys in the .env file in the server folder?

Any suggestions or comments on improvement?
@hanseaston hanseaston added enhancement enhancement on an existing feature ideas wanted Need ideas and inputs from others backend easy fix! normally can fix in just a few lines of code! labels Aug 9, 2020
@neverdue neverdue mentioned this issue Aug 15, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backend easy fix! normally can fix in just a few lines of code! enhancement enhancement on an existing feature ideas wanted Need ideas and inputs from others
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hanseaston