Hey @z3APA3A, long-time user here (10+ years), so first - genuinely, thank you. 3proxy is one of those rare tools that does exactly what it says and never gets in your way.

I want to ask about something I've been dealing with for years - using 3proxy in Docker and Kubernetes.

Right now it's a bit painful. No env var support means you have to manage config files somehow. No arm64/arm/v7 builds. No static binary, so you can't run it in a scratch/distroless image. No healthcheck. No Helm chart. None of these are dealbreakers on their own, but together they add a lot of friction for anyone trying to run it in a modern container setup.

So about 6 years ago, I put together tarampampam/3proxy-docker to fix all of that for myself, and it kind of took on a life of its own. What it adds:

• env var config (PROXY_LOGIN, PROXY_PASSWORD, PROXY_PORT, etc.) - no config file needed
• static binary running in a scratch image - zero OS, minimal attack surface
• multi-arch: amd64, arm64, arm/v7, ppc64le, s390x
• Lua entrypoint for startup logic - sounds like an odd choice, but it turned out surprisingly solid and easy to extend without rebuilding the image
• built-in healthcheck
• Helm chart on Artifact Hub
• JSON-structured logs
• standalone pre-compiled binaries in releases (no Docker required)

I've been maintaining it ever since, and it's got decent usage.

So my questions:

1. Is there any interest in making 3proxy itself more container-friendly upstream? Even just env var support and a static build would go a long way.
2. If not, would you consider adding a link to my repo in the README for people who want a ready-to-go Docker/Kubernetes setup? If you're open to it, I'm happy to open a PR with the change myself.