How matsuridayo/nekoray works
Project type and purpose
• The user interacts with a Qt-based frontend to configure and manage multiple proxy protocols (SOCKS, HTTP(S), Shadowsocks, VMess, VLESS, Trojan, TUIC, etc.).
File structure
• Top-level build and config: CMakeLists.txt, .github/workflows, cmake/, libs/ (build & deploy scripts).
• Frontend/UI (C++/Qt):
• main/, ui/, res/, translations/ (all *.cpp, *.hpp, *.ui, resource files)
• sys/ (platform abstractions for Windows/Linux)
• Business logic & data:
• db/ (ConfigBuilder, Database, ProxyEntity, TrafficLooper)
• fmt/ (serializing internal “Beans” to core config objects)
• RPC layer:
• rpc/ (gRPC client stubs and helpers gRPC.cpp/h)
• Third-party libs in 3rdparty/ (Qv2ray, protobuf, yaml-cpp, zxing, QHotkey, etc.)
• Go backend:
• go/grpc_server (proto definitions, generated Go stubs)
• go/cmd/updater (self-update service)
• Tests & docs: test/, docs/, README.md
README for additional insights
• Lists supported protocols, subscription parsing, run flags.
• References technical docs (RunFlags.md, Build instructions).