How cikian/cikpier works
CikPier is a Windows graphical client for the official frpc executable. Users enter server settings in the first-run wizard, then manage proxies and inspect translated connection logs through the UI; Go backend methods coordinate configuration, the frpc process, and its local Admin API. The README also documents diagnostics, port prechecks, tray/startup behavior, architecture warnings, and visitor proxies. Those capabilities are represented at their documented source locations; implementation details beyond the excerpts are not assumed.
Main entry points: app.go App methods · main.js Client UI · manager.go Process manager · client.go Admin API client
Components 13
User experience
- Client UI
app/frontend/src/main.js
Application orchestration
- App methods
app/app.go - Bound operations
app/export.go - Connection config
app/internal/cfgfile/cfgfile.go - Wails entry
app/main.go
frpc runtime
- Process manager
app/internal/frpcman/manager.go - Log translation
app/internal/frpcman/logparse.go - Admin API client
app/internal/frpcapi/client.go
Windows integration
- Tray integration
app/tray.go - Status icons
app/trayicon.go - Architecture hints
app/arch.go
Other components
- User
- Official frpc
Connections 12
- User → Client UI: uses
README.md - Client UI → Bound operations: invokes
app/frontend/src/main.js - Wails entry → App methods: creates and binds
app/main.go - App methods → Connection config: reads and saves
app/app.go - App methods → Process manager: starts and stops
app/app.go - App methods → Admin API client: manages proxies
app/app.go - Process manager → Log translation: parses output
app/internal/frpcman/manager.go - Process manager → Official frpc: launches and monitors
app/internal/frpcman/manager.go - Admin API client → Official frpc: HTTP requests
README.md - Tray integration → Status icons: uses status icons
- App methods → Tray integration: reports connection state
- Client UI → Architecture hints: shows architecture warning