Arvan Reseller؛ افزونه فروشندگان ابر آروان

An independent WordPress plugin that lets an ArvanCloud reseller sell Cloud Servers, CDN and Object Storage on their own site: display, ordering, provisioning through the ArvanCloud APIs, hourly metering, prepaid-wallet billing, and automatic service suspension/termination that mirrors ArvanCloud's documented policy per product.

Repository: https://github.com/MMTE/arvancloud-reseller-plugin

Zero dependencies: no WooCommerce, no ACF, no theme requirements, no Composer at runtime. Vanilla PHP (7.4+/8.x), core-bundled Sodium for secret storage, WP REST API, vanilla JS/CSS (Sorkhab design system, Persian RTL native).

Status (2026-08-22): all three categories (سرور ابری، شبکه توزیع محتوا (CDN)، فضای ابری (Object Storage)) are implemented end-to-end. Every interface is locked in docs/CONTRACTS.md; every decision is traced in docs/adr/DECISIONS.md. This README ships final facts only: see CHANGELOG for live progress.

What it does

Product coverage — end-to-end per category [D-036]

Metering honesty [D-039]: live OBS storage is exact (x-rgw-bytes-used); egress and requests are billed only on plugin-proxied traffic because the S3 API exposes no per-bucket counters — nothing is estimated. CDN fair-use caps are reseller-set defaults (ArvanCloud publishes no number).

Extensibility — REST first

«رابط REST سطح توسعه‌پذیری است؛ صفحات تنها یک مصرف‌کننده‌اند.» The shipped storefront and account pages are one consumer of the arvan/v1 REST surface; any theme or custom frontend can drive the same journeys through Products::checkout_url( $category, $params ) deep links plus the REST contract (GET /catalog, POST /me/orders, GET /me/services, …). No cart and no SKU abstraction are layered on top: the order/configuration model is the commerce layer.

Install

1. Copy arvan-reseller/ into wp-content/plugins/ and activate — no other plugin, theme change, or core modification needed.
2. The onboarding wizard starts: Machine-User access key (+ optional extra keys per purpose) → hackathon access token (validated against the embedded allow-list) → organization info → storefront template → financial rules.
3. Pages are generated automatically (فروشگاه، سرور ابری، CDN، Object Storage، کیف پول، داشبورد، فاکتورها، …).
4. Driver mode: sandbox (deterministic, demo-safe) or live (real ArvanCloud API). Sandbox is default.

Dev quick-start (Local by Flywheel): the repo symlinks into the site; bin/wp wraps wp-cli with the Local PHP/MySQL environment.

Documentation map

Scope (per the challenge)

All three categories — Cloud Server, CDN and Object Storage — are implemented end-to-end [D-036]: product pages, checkout, provisioning, hourly metering, per-product suspension ladders and settlement. Real payment integration is out of scope (mock gateway + receipt registration). GPU flavors, volumes/snapshots UI, VNC are out of scope. Live S3 keys for external clients are a reseller manual step (the S3 API provisions none); live OBS egress/request metering is plugin-proxy-only [D-039].

License

GPL-2.0-or-later.

Demo quick-start (local)

1. bin/wp arvan seed --reset: demo customers (ali.demo/sara.demo/reza.demo, Passw0rd!, dev-only), wallets, services, history. ali.demo owns one service per category: cloud-server sbx-seed-ali, CDN domain shop-cdn.ir (بسته رشد), OBS bucket ali-media (growth, ~80 GiB incl. banner.png); the storefront, account panes and reseller panel all render this state immediately.
2. bin/wp arvan test-driver — per-product connection test rows (cloud-server / cdn / object-storage) against the active driver mode; live read-only validation uses the stored keys (Authorization: Apikey …, S3 pair).
3. Re-run the onboarding wizard on camera: bin/wp option update arvan_onboarding_complete 0 && bin/wp option update arvan_wizard_skipped 0 → wp-admin → فروشندگان آروان (sidebar label; full brand «افزونه فروشندگان ابر آروان» on the page title).
4. Mailpit (emails): http://localhost:10000 — Persian RTL threshold/negative/ladder mails (incl. the per-product CDN hold/DNS-off and OBS write-cut/read-cut/purge templates).
5. Sandbox driver default; live read-only validated (Authorization: Apikey <key>). Cron manual: bin/wp arvan cron arvan_billing — one pass bills all three categories (flavor hours, CDN plan fee + egress/requests, OBS plan fee + storage).
6. CDN demo journey: storefront → شبکه توزیع محتوا → domain + بسته رشد → checkout → fund → order → active detail (CNAME guidance) → cron → plan-fee + egress + requests rows in the ledger.
7. OBS demo journey: storefront → فضای ابری → bucket (growth, ir-thr-at1) → checkout → order → credentials «نمایش یک‌باره» → object browser (list/upload/download/delete on the seeded ali-media files) → cron → plan-fee + storage rows.
8. Site: http://localhost:10003 (admin/mahdi1234).

Security note: seeded demo accounts use a fixed dev password (Passw0rd!) — local/dev environments only; rotate or disable seeding on any public site. Live credentials live only in ~/.arvan-creds.json and the encrypted wp_arvan_api_keys row; the repo contains no secrets.