Codex/add image and file loading support - #161
Conversation
added DOCKER_IMAGE_FRONTEND and DOCKER_IMAGE_BACKEND env variables Signed-off-by: Dmitry Denisenko <Dmitry_denisenko@mckinsey.com>
Added DOCKER_IMAGE_FRONTED and DOCKER_IMAGE_BACKEND as env variables for workflows Signed-off-by: Dmitry Denisenko <Dmitry_denisenko@mckinsey.com>
Added QDRANT__SERVICE__API_KEY to env for staging workflow Signed-off-by: Dmitry Denisenko <Dmitry_denisenko@mckinsey.com>
Added
USER_AGENT
MAX_WORKERS
BACKEND_CORS_ORIGINS
USERS_OPEN_REGISTRATION
POSTGRES_PORT
POSTGRES_DB
OPENAI_API_KEY
to staging workflow
Signed-off-by: Dmitry Denisenko <Dmitry_denisenko@mckinsey.com>
added openai_api_key as env variable Signed-off-by: Dmitry Denisenko <Dmitry_denisenko@mckinsey.com>
Added POSTGRES_USER to staging workflow Signed-off-by: Dmitry Denisenko <Dmitry_denisenko@mckinsey.com>
added
DENSE_EMBEDDING_MODEL
SPARSE_EMBEDDING_MODEL
to staging workflow
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Added
MAX_MEMORY_PER_CHILD
MAX_UPLOAD_SIZE
RECURSION_LIMIT
to staging workflow
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Removed .env Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Added PROJECT_NAME to staging workflow Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Added some missing .env variables to backend Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Added
QDRANT__SERVICE__API_KEY
USER_AGENT
MAX_WORKERS
BACKEND_CORS_ORIGINS
USERS_OPEN_REGISTRATION
POSTGRES_PORT
POSTGRES_USER
POSTGRES_DB
OPENAI_API_KEY
DENSE_EMBEDDING_MODEL
SPARSE_EMBEDDING_MODEL
MAX_MEMORY_PER_CHILD
MAX_UPLOAD_SIZE
RECURSION_LIMIT
PROJECT_NAME
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Dropped container_name for celery in docker-compose.yml (to not trigger conflict while trying to run staging and production at the same server) Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
trying approach without subdomains Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
removed https from docker-compose will keep only http Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
removed missing env variables and celery container Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
fixed indentation error Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Signed-off-by: Dmitry Denisenko <dmitriy.denisenko@outlook.com>
Changed run command once again
switched to running separate file with script to init n8n db
Russification
Adding n8n configuration and init scripts
….2-models Add GPT-5.1 and GPT-5.2 OpenAI worker model choices
…dated-code Codex-generated pull request
…ovider-integration-tests-for-openai-an Follow-up: ensure attached images are sent as images to providers
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 11090108 | Triggered | Generic Password | ed3b287 | backend/tests_integration/test_provider_chat_integration.py | 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 secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.
No description provided.