mirror of
https://github.com/Rain-kl/OpenFlare.git
synced 2026-10-05 15:26:36 +08:00
ryan
454542c1d0
- README 默认英文：README.en.md → README.md（英文为默认），中文移至 README.zh-CN.md，语言切换链接同步 - 恢复被删除的 docs/en/ 英文文档（git 历史 cc5e53c5^），删除 4 篇已废弃文件 - 英文导航 config.ts 对齐中文结构（新增 Deployment/Changelog 侧栏，同步 Guide/Design 条目） - 翻译 15 篇中文新增文档：guide 5 篇（certificates/pages-usage/proxy-config/uptime-kuma/zone-domain-migration）+ design 10 篇（zone-design/cloudflare-pointing/waf-orchestration/origin-error-page/edge-cache-design/pages-design/logstore/kuma-design/login-captcha/observability 三篇） - en 首页更新（新增 Pages 特性、tagline 同步）；changelog 英文入口指向中文版 - vitepress 构建验证：43 个英文页面全部渲染 注意：29 篇旧英文文档为恢复版，部分内容（如 deployment/server、reference/configuration）可能落后于中文，需后续逐篇同步
28 lines
2.0 KiB
Markdown
28 lines
2.0 KiB
Markdown
# Credits
|
|
|
|
OpenFlare is essentially a solution integration project. During its design and implementation phases, it drew inspiration from the exceptional concepts, architectural designs, and technical achievements of numerous open-source projects. Below are the key upstream open-source projects OpenFlare relies on for its core engine, security mechanisms, and backend/frontend system frameworks, along with our sincere thanks to these projects and their active communities.
|
|
|
|
---
|
|
|
|
### 1. OpenResty
|
|
* **Project Positioning**: A high-performance Web platform based on Nginx and Lua.
|
|
* **Role in OpenFlare**: Acts as the edge gateway for the global Data Plane. All public web traffic is received by OpenResty first, where high-concurrency HTTPS handshakes, WAF security rule evaluations, and PoW CC verification are performed before executing reverse proxies.
|
|
* **Project Link**: [OpenResty Official Website](https://openresty.org/)
|
|
|
|
### 2. FRP (Fast Reverse Proxy)
|
|
* **Project Positioning**: A high-performance reverse proxy application focused on intranet penetration.
|
|
* **Role in OpenFlare**: Serves as the underlying tunnel engine for the intranet penetration subsystem. The relay-side manager `openflare-relay` is responsible for running and scheduling the `frps` engine, while the intranet client `openflared` is responsible for generating TOML configurations locally and running the multiplexed `frpc` subprocesses.
|
|
* **Project Link**: [fatedier/frp (GitHub)](https://github.com/fatedier/frp)
|
|
|
|
---
|
|
|
|
### 3. Anubis (PoW Solution)
|
|
* **Project Positioning**: A lightweight human-machine verification and protection solution based on Proof of Work (PoW).
|
|
* **Role in OpenFlare**: Provides the core **seamless PoW CC challenge** capabilities for the gateway WAF.
|
|
|
|
---
|
|
|
|
### 4. gin-template
|
|
* **Project Positioning**: A modern full-stack development boilerplate based on Go Gin and frontend builds.
|
|
* **Role in OpenFlare**: Provided the standard, unified backend/frontend system architecture baseline for the OpenFlare control plane (Server).
|