👋 @HADB

Where do the HTTP_PROXY and HTTPS_PROXY environment variables come from? Have they been documented somewhere?
I don't think we have them anywhere in the code base.

@ruslandoga Hi, thanks for replying. HTTP_PROXY and HTTPS_PROXY are environment variables used to specify proxy servers for HTTP and HTTPS traffic respectively. Many applications and libraries recognize and use these variables to route their network traffic through specified proxy servers, such as：curl, wget and Python’s requests library.

I see. We might be able to provide support for these env vars later, but for now we can at least make proxying configurable via custom config files. I'll open a PR for that later today with an example configuration.

@HADB would you be able to try out the image I built from #4270?

Here're the changes you'd need to make:

_{docker-compose.yml}

plausible:
- image: ghcr.io/plausible/community-edition:v2.1.1
+ image: ghcr.io/ruslandoga/plausible:build-allow-finch-config-9456444
+ volumes:
+   - ./my_config.exs:/app/my_config.exs

_{my_config.exs}

import Config

# Plausible uses HTTPS for all outgoing requests, and our HTTP client (Mint) doesn't support HTTPS->HTTPS proxying
# https://hexdocs.pm/mint/Mint.HTTP.html#connect/4-proxying recommends HTTP->HTTPS in this case
config :plausible, Plausible.Finch, conn_opts: [proxy: {:http, _host = "some.proxy.com", _port = 1080, _opts = []}]

Note that you would need to provide your own proxy host/port pair. There is also an example config in #4270 where host and port are extracted from HTTP_PROXY env var.

_{plausible-conf.env}

+ EXTRA_CONFIG_PATH=/app/my_config.exs

@ruslandoga I have tried this image and it works as expected! Great job! Thanks a lot!