Commit graph

3 commits

Author SHA1 Message Date
91a8a4374b site: mark backup/restore as shipped on the landing comparison table
Was 'в разработке' — done as of f586cf9.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-12 10:24:18 +05:00
cfac7c1445 site: landing install command now routes through our own site, not raw github clone
Was: git clone https://github.com/devsavsis/mbs-panel.git && cd mbs-panel && sudo bash install.sh
Now: bash <(curl -Ls https://mbs.savsis.xyz/install.sh)

Matches the one-liner pattern already used for node installs
(nodeprov.ONE_COMMAND_TEMPLATE). install.sh itself already prefers the
api.savsis.xyz mirror over github.com for the actual repo clone (see
2604c2d) — this just stops sending first-time visitors through a raw
github.com URL as the very first step, before that fallback logic even
runs. mbs.savsis.xyz/install.sh is served as a static file kept fresh
by the existing mirror-sync cron (extended to export it on every sync).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-12 09:54:11 +05:00
54dc9e2dae site: project landing page, deployed at mbs.savsis.xyz
Standalone marketing/docs page for the mbs-panel project itself (not
the customer-facing site/ template that ships with installs) — what it
is, feature grid, an honest comparison table vs Remnawave/Marzban
(sourced from docs.rw's own comparison page), architecture, and a
step-by-step install guide with the clone-and-run command.

Same dark design system as site/index.html (colors, easing, scroll
reveal) for visual consistency across everything savsis.xyz.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-12 09:43:28 +05:00