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.

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

Adjust Logs Based on Development or Production Environment #23

Open
nkkko opened this issue Sep 26, 2024 · 2 comments
Open

Adjust Logs Based on Development or Production Environment #23

nkkko opened this issue Sep 26, 2024 · 2 comments

Comments

@nkkko
Copy link
Member

nkkko commented Sep 26, 2024

Is your feature request related to a problem? Please describe.
The current logging setup does not distinguish between development and production environments, potentially exposing sensitive information in production logs while making it difficult to debug in a development setting.

Describe the solution you'd like

  • Introduce an environment variable (ENVIRONMENT) to specify whether the application is running in development or production mode.
  • Adjust log levels and formats based on the value of this environment variable:
    • Development: Detailed logs with debug information.
    • Production: Essential logs with warning and error information only, potentially in a more secure format.

Describe alternatives you've considered

  • Keeping a single log configuration for all environments, which risks either verbose logs in production or insufficient information in development.

Additional context
Add necessary checks and configuration adjustments in main.py and ensure the environment variable is considered in the logging setup. Thoroughly test the different log levels and formats to confirm the behavior aligns with the environment specified.

@nkkko
Copy link
Member Author

nkkko commented Oct 9, 2024

/bounty $10

Copy link

algora-pbc bot commented Oct 9, 2024

💎 $10 bounty • Daytona

Steps to solve:

  1. Start working: Comment /attempt #23 with your implementation plan
  2. Submit work: Create a pull request including /claim #23 in the PR body to claim the bounty
  3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

If no one is assigned to the issue, feel free to tackle it, without confirmation from us, after registering your attempt. In the event that multiple PRs are made from different people, we will generally accept those with the cleanest code.

Please respect others by working on PRs that you are allowed to submit attempts to.

e.g. If you reached the limit of active attempts, please wait for the ability to do so before submitting a new PR.

If you can not submit an attempt, you will not receive your payout.

Thank you for contributing to daytonaio/devcontainer-generator!

Add a bountyShare on socials

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant