IRNova/Nova-Proxy: README-based editorial guide
A guide grounded in the README, repository metadata, and license for installing and checking IRNova/Nova-Proxy.
Project scope
IRNova/Nova-Proxy describes itself in the README as "یک پنل گرافیکی کاربردی برای ارائه اشتراکهای Worker با پروکسیهای ، Trojan و Warp به همراه زنجیره پروکسی، ارائه دهنده تنظیمات کامل DNS، IP تمیز و روتینگ پیشرفته برای کاربران تمامی پلتفرمها با استفاده از هستههای Amnezia، Wireguard،". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "README", the README says: Your own censorship-resistant proxy with a full admin panel, on a single Cloudflare Worker.. That establishes the project's stated boundary, not a production test.
Suitable use cases
The README's "Features" section gives a useful starting point for deciding whether the project fits: Resistance Policy presets: routing tuned for Iran and other high-censorship networks (port spread, domestic bypass, ad and tracker blocking, and more), each with a plain-language on/off.. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Multi-user management with per-user quota, expiry, daily limits, and one private link each.. It can shape a first test, but it does not replace testing in the intended environment.
How it works
The operating model is spread across sections such as "What it is". The source evidence includes: Nova Proxy is a control panel and edge worker that runs on Cloudflare Workers. You deploy it to your own free Cloudflare account, so the bandwidth, the domain, and the data are all yours. There is no shared server and no middleman.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.
Installation and first run
Start installation from the README's documented entry point. A command that can be checked in the source is: # 1. install the Cloudflare CLI npm install -g wrangler wrangler login # 2. install dependencies and deploy # Wrangler provisions and binds KV and D1 automatically. npm ci npm run deploy When the README contains no runnable command, this article does not invent one. Open its "What it is" section and confirm system dependencies, default ports, and first-run initialization before using a public server.