How houtadono/proxy-wright works
Project Type and Purpose
• Proxy-Wright is a desktop application (full-stack on the client side) for managing browser profiles and proxies, launching Playwright browsers with user-defined settings, and self-updating via GitHub Releases.
• Built in Python, it uses PySide6 for the UI, Playwright for browser automation, and an embedded 3proxy binary for SOCKS5 proxy support.
File Structure Analysis
• Top-level entrypoints:
• app.py (main application startup)
• app.spec / updater.spec (PyInstaller build specs)
• installer.iss (Inno Setup installer script)
• Configuration & core logic:
• config.py (static config values)
• core/ (paths.py, settings.py, updater.py)
• Data layer:
• data/db.py (SQLite or similar persistence)
• data/repo.py (repository pattern for profiles & settings)
• Service layer:
• services/browser_service.py (Playwright browser lifecycle)
• services/playwright_service.py (Playwright API wrapper)
• services/proxy_service.py (3proxy wrapper + native proxy config)
• services/qt_event_runner.py (bridging Qt’s event loop and async tasks)
• UI layer:
• ui/main_window.py
• ui/profile_dialog.py, proxy_dialog.py, setting_tab.py
• Background workers:
• workers/browser_worker.py
• workers/proxy_check_worker.py
• workers/update_worker.py
• Utilities & scripts:
• tools/updater_helper.py
• .github/scripts (release notes, cleanup)
• External binaries & assets:
• bin/3proxy.exe (embedded proxy server)
Key README Insights
• Multi-language support (via Qt .qm files)
• In-app update checking from GitHub
• Uses PyInstaller packaging, so bundling of dependencies and 3proxy.exe
• License restrictions (source-available, non-commercial)
Components
a. Frontend (UI)
• PySide6-based windows & dialogs
• Translations & resource loading
b. Business Logic / Controllers
• core/updater: checks & downloads new releases
• services/*: abstractions over Playwright, 3proxy, proxy setup
c. Data Persistence
• SQLite (or file-based DB) via data/db.py
• Repository layer (data/repo.py)
d. Background Workers
• Threads or QtConcurrent tasks for non-blocking operations
e. External Dependencies
• 3proxy.exe binary (launched as a subprocess)
• Playwright browsers (Chromium, Firefox, WebKit)
• GitHub Releases API (for update service)
f. Packaging & Deployment
• PyInstaller (app.spec, updater.spec)
• Inno Setup installer (installer.iss)
Relationships & Data Flow
• UI events → controllers in services or core → data repo or external processes
• Services spawn workers for I/O (network, proxy health check, browser launch)
• Workers report status back to UI via signals/events (qt_event_runner)
• Updater downloads new build → PyInstaller-generated updater.exe → restarts app
• 3proxy subprocess launched by proxy_service, managed by browser_service when launching browsers
Architectural Patterns & Design Principles
• MVC/MVP-like pattern: UI layer (View) separated from services (Controller) and data (Model)
• Repository pattern for data access
• Service layer for external integrations (Playwright, 3proxy)
• Asynchronous/background workers to keep UI responsive
• Single-page desktop UI with multiple dialog components