Backend #1
Open
Backend #1
Conversation
This file contains hidden or 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
…nment - Set up services for FastAPI backend, PostgreSQL, Redis, ChromaDB, and optional Next.js frontend. - Include health checks for each service. - Configure environment variables for database and API connections.
test(unit): add unit tests for authentication service, chunking utilities, database models, and security utilities
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 26339814 | Triggered | Generic Password | 1be3711 | backend/app/schemas/auth.py | View secret |
| 26339815 | Triggered | Generic Password | 1be3711 | backend/app/schemas/user.py | View secret |
| 13009185 | Triggered | Generic Password | 19f68f9 | .github/workflows/backend-tests.yml | 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.
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.
This pull request introduces essential setup files and documentation for running, testing, and deploying the ExploitRAG backend. The main changes include new quick start guides, Docker configuration files, environment variable templates, and a GitHub Actions workflow for backend tests. These additions streamline onboarding, local development, CI/CD, and containerization.
Documentation and Quick Start Guides:
QUICK_START.mdandQUICK_START_HYBRID_AGENT.mdwith step-by-step instructions for running the backend, configuring services, ingesting data, using agent search, troubleshooting, and verifying setup. These guides cover both standard and hybrid/agent modes, including example API calls and feature explanations. [1] [2]Environment and Configuration Files:
backend/.env.exampleandbackend/.env.testto provide example environment variable configurations for development and testing, including database, Redis, ChromaDB, JWT, Gemini API, and rate limiting settings. [1] [2]Docker Support:
backend/Dockerfilefor building and running the backend in a container, including multi-stage builds for optimized image size, health checks, and non-root user setup.backend/.dockerignoreto exclude unnecessary files from Docker build context, improving build speed and reducing image size.Testing and CI/CD:
.github/workflows/backend-tests.ymlto automate backend tests on pushes and pull requests, including service setup (Postgres, Redis), linting, test execution, coverage reporting, and badge generation.Git Ignore Updates:
backend/.gitignoreto exclude build artifacts, environment files, IDE/project settings, data files, logs, and other non-essential files from version control.