It transforms R2R from a "demo-friendly" framework into a .
If you are diving into the world of R2R (RAG to Riches) —the popular open-source framework for building and scaling Retrieval-Augmented Generation pipelines—you might have stumbled across a file named team.r2r.root.certificate-r2r.rar . team.r2r.root.certificate-r2r.rar
export REQUESTS_CA_BUNDLE=/path/to/extracted/r2r-ca-root.crt # Then run your R2R client commands r2r serve --host your-internal-r2r.com Add this to your docker-compose.yml : It transforms R2R from a "demo-friendly" framework into a
sudo cp r2r-ca-root.crt /usr/local/share/ca-certificates/r2r-ca.crt sudo update-ca-certificates team.r2r.root.certificate-r2r.rar
At first glance, a .rar archive containing a root certificate might seem out of place in a standard Python RAG project. However, this file is a critical piece of the puzzle for teams running R2R in .
volumes: - ./r2r-ca-root.crt:/etc/ssl/certs/r2r-ca.crt:ro environment: - REQUESTS_CA_BUNDLE=/etc/ssl/certs/r2r-ca.crt Run an R2R health check using the custom CA: