-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Prod push #222
Prod push #222
Conversation
* Remove unused cache purge * Use django-environ to read config from env * Pin dependencies for reproducible builds * Add dockerize and a simple entrypoint
* Collect translations for custom model validations * Show for now non field errors * Add autoclean and xor mixin to help with model field validations * Remove unsed script * Add basic tests * Freeze pytest requirements * Remove unused autosavemixin * Remove debugging flag * Add some pertinent comments * Run tests on gha * Test running actions from containers
* Format everything with black * Added black as dev requirement * To be consistent, use a line-length of 80 * Check formatting with black, via Github action Added from seismic-risc: code4romania/seismic-risc@0a7de6c * Add small documentation about black * Run black on pull request * Fix formatting * Small typos fixes * Fix linting after upstream rebase * Catch all cases for xor mixin model * Combine linting with running tests * Update from a 80 line length limit to 120
Bumps [django](https://github.com/django/django) from 2.2.9 to 2.2.10. - [Release notes](https://github.com/django/django/releases) - [Commits](django/django@2.2.9...2.2.10) Signed-off-by: dependabot[bot] <support@github.com>
* Add a seed command * Add row number in templates * Correctly set docker-compose's env * No need for directory listing * Clean unused code * Use only moonsheep's production mode * Show for errors in html * Add support for row number in models and forms * Adapt tasks to moonsheep's production mode * Wait for a longer period of time * Seed all the time * Update development instructions * Remove debug leftovers
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
- | Generic Password | 175ebf8 | project_template/settings/dev.py | View secret | |
- | Generic Password | 175ebf8 | .env | View secret | |
- | Generic Password | 175ebf8 | database.env | 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!
No description provided.