[Bug] `manage.py` fails over TLS in shell sessions: default `RDS_TLS_CA_PATH` doesn't match where the entrypoint saves the CA
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Read settings.py where RDS_TLS_CA_PATH defaults to /app/ca-cert.pem, then trace both CA download branches in entrypoint.sh and how it writes /run/chaotica.env. Pick a fix that makes shell sessions use the CA file that exists, and verify that a manage.py command works with RDS_TLS_USE and RDS_TLS_URL set without manually exporting the path.
Written by the indexing model from the issue text.
Description
Summary
With RDS_TLS_USE and RDS_TLS_URL set, entrypoint.sh downloads the CA bundle to /app/rds-ca-cert.pem and exports RDS_TLS_CA_PATH for the processes it starts. But settings.py falls back to a different file:
"ca": os.environ.get("RDS_TLS_CA_PATH", "/app/ca-cert.pem")
/app/ca-cert.pem is only written when RDS_TLS_CA (base64) is used instead of RDS_TLS_URL. Any process not started by the entrypoint, such as docker exec, kubectl exec or ECS Exec, doesn't inherit the export. So every manage.py command fails:
django.db.utils.OperationalError: (2026, 'TLS/SSL error: No such file or directory (2)')
The workaround is export RDS_TLS_CA_PATH=/app/rds-ca-cert.pem before running commands.
Suggested fix
Any of these:
- Use one path: have both branches of
entrypoint.shwrite to the same file, and make it the default insettings.py. - Fall back to whichever file exists: in
settings.py, use/app/rds-ca-cert.pemor/app/ca-cert.pem, whichever is present. - Make shells see it: write the export to a profile file (for example
/etc/profile.d/chaotica.sh) so interactive shells pick it up. The entrypoint already writes/run/chaotica.envfor supervisord.
- Dominant language
- HTML
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from brainthee/CHAOTICA
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
[Minor UI Bug] Client page shows account manager photos as squares overlapping the round borderOpen
Difficulty 1/5 Under an hour Newbie friendliness 94/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
All issues in brainthee/CHAOTICA
Similar issues
-
dropIndexes by key pattern panics on a shorter pattern and drops the wrong index on a longer oneOpen
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mega-yfue/ha-eufy-sdk-bridge#198 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
qte77/agentic-job-offer-to-application-kit#487 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
btclib-org/btclib-wallet#801 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 2 days