-
Notifications
You must be signed in to change notification settings - Fork 2
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
Initialize database using alembic migrations #258
Conversation
ffd1e35
to
24dbe22
Compare
5f61377
to
2d85668
Compare
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
8431139 | Generic High Entropy Secret | e866055 | backend/src/configs/default.yaml | View secret |
8431140 | Generic High Entropy Secret | b904e44 | docker/.env.example | View secret |
8431140 | Generic High Entropy Secret | e866055 | backend/.env.example | View secret |
8431140 | Generic High Entropy Secret | e866055 | docker/.env.example | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
e8af72b
to
b904e44
Compare
Fixes #254
Since the new migration is skipped when the
user
table already exists, it should do nothing on existing production systems. On new development setups, migrations should now work fine.I've updated the relevant section in the developer guide as well.