Skip to content

Proxy Workbench v2.0.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 24 Sep 21:52
· 31 commits to df93b175c4e6815e60e4236a099ce4af7b0b7cb5 since this release
v2.0.0
a4ccd55

Added

  • Windows executable: every release ships proxy-workbench-…-windows-x64.exe built with PyInstaller. It opens the GUI on double-click, runs the CLI with arguments, and keeps its data in a data folder next to itself; no Python needed.
  • pipx install (#3): pipx install git+https://github.com/DavidVoitenko/proxy-workbench gives a proxy-workbench command. Without arguments it opens the GUI; with arguments it runs the CLI (python -m proxy_workbench works too). Releases also attach the wheel.
  • Docker Compose: compose.yml runs a checker that keeps 100 proxies fresh, the API and the rotating proxy from one shared volume.
  • Quick pre-check (--prefilter, on by default with 512 connections; GUI: Performance → Quick pre-check). A plain TCP connect runs before the full check, so addresses that do not even accept a connection (most of any public list) are dropped at a fraction of the cost. They are stored as UNREACHABLE, so a stopped scan resumes where it left off.
  • End-to-end package check: packaging/smoke.py installs nothing and touches no public network. It starts the built app, runs a check through a local mock proxy and reads the result back through the API and the gateway. CI runs it for the wheel on Linux and Windows and for the Windows executable; releases run it before publishing.

Fixed

  • On Windows, background checks started from an environment without PYTHONUTF8 (the new .exe and pipx installs) failed on the first Cyrillic log line. Terminal output is now always UTF-8.

Changed

  • The code now lives in the proxy_workbench package. proxytool.py, gui.py, Start.bat, Start.command and run.sh keep working from a source folder, and an existing data/ folder there is used as before.
  • The data folder is chosen as follows: PROXY_WORKBENCH_DATA, then data/ in a source checkout or next to the .exe, then the user profile for pipx installs.
  • The Docker image sets PROXY_WORKBENCH_DATA=/app/data.
  • The GUI starts its checks as python -m proxy_workbench …, or through the executable itself when frozen.

What's Changed

  • Release 2.0.0: Windows executable, pipx install, Docker Compose by @DavidVoitenko in #20

Full Changelog: v1.9.0...v2.0.0

Contributors

DavidVoitenko
Assets 7
Loading