Implemented Backend logging framework #12
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…iguration for determining server environments.
swoocn
requested review from
zolcsi,
soleil00,
DarinHajou and
BlueJacobianPioneer
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[see commits]
Log levels for frontend and backend will be set to ERROR outside of localhost and sandbox, otherwise it will be set to DEBUG. This may change once we integrate with a logging service or DB.
@soleil00 - we need to build a VERCEL_ENV variable in Vercel and set it to a value to indicate a non-development server i.e., PROD. Let me know if you have any questions!