Support HTTP proxies for web requests

[dogversioning]

Pretty standard territory on this one - https://www.scrapingbee.com/blog/python-requests-proxy/ , among other resources explaining the same - we just need to decide how we want to inject it (perhaps a .ENV file).

[mikix]

I thought this stuff was baked into python libraries (with code overrides allowed). Like, that blog post suggests you can just set:

export HTTP_PROXY='http://10.10.10.10:8000'
export HTTPS_PROXY='http://10.10.10.10:1212'

I'd hope that would work as-is...? If not, yeah let's fix that.

[mikix]

Oh ah -- you are thinking about how to drive the compose file. This is a docker-setup ticket, yeah?

[dogversioning]

Yeah - there's basically two best practices ways to do it in docker:

• have an .env file in the same directory as the compose
• have a compose.override.yaml to map additional variables into specific containers

[kangnari]

Does the cTAKES container also require any outbound access?

[mikix]

Does the cTAKES container also require any outbound access?

I believe so yes, because it downloads the UMLS database.

[dogversioning]

yeah, that might be a bit trickier to wrangle.