How bklockly/proxyz works
Project Type & Purpose
• Proxyz is a full-stack application meant to manage and switch proxy IPs. It has a Go-based backend (using the Wails framework) and a modern frontend built with Vue.js.
• The tool listens on a local address (127.0.0.1:1080) and can both import proxy files and attempt to crawl free proxy lists. The README makes clear that it is intended for research and authorized testing.
Analyzing the File Structure
• Top-Level Overview:
– Backend: Contains directories like client, config, info, and request. The “client” subdirectory holds modules (app.go, start.go, etc.) for managing connections, logging, and responses.
– Frontend: Contains the Vue.js application (components, assets, main.ts, etc.) plus additional Wails-related JavaScript (wailsjs folder). This indicates that the frontend communicates with the Go backend through the Wails runtime.
– Build: Packaging scripts and installer configurations for different platforms (Darwin and Windows). This suggests that after building, the application is bundled for desktop platforms.
– Static: Contains assets like images shown in the README for previewing proxy status.
– Configurations: Files like wails.json, go.mod, and various installer scripts provide deployment and dependency info.
Key Architecture Components
a. Frontend Layer:
– Wails Runtime: Show how the frontend leverages the Wails JavaScript bridge (wailsjs folder) to interact with the backend.
b. Backend Layer:
– Go Application (Main.go entry point): Indicate that the backend is written in Go with modular directories:
• Client: Handles operations related to starting the service, logging, managing responses.
• Config: Loads and manages configuration parameters.
• Request: Contains modules that deal with fetching or processing proxy requests (like pr_89.go, pr_happy.go, etc.).
• Info: Likely used to display or manage meta-information about the proxy pool status.
– Local Proxy Server: Highlight that the backend continuously listens on 127.0.0.1:1080 to serve or proxy requests.
c. Build & Deployment:
– Build Scripts: Separate modules that package and produce installers for macOS (Darwin) and Windows environments.
– Indicate deployment artifacts or compiled executables (e.g., wails.exe, Info.plist) as part of the packaged application.
d. Interconnections:
• The Vue.js UI sends requests/invocations through the Wails framework.
• The backend processes proxy configurations, manages the dynamic switching of IPs, and feeds status updates back to the frontend.
– Optionally, illustrate logging/response flows and data exchange (like config changes or proxy updates).