Skip to content

GOST Manager v2.0.0

Choose a tag to compare

@github-actions github-actions released this 14 Jul 17:49
· 6 commits to main since this release
d625b83

GOST Manager v2.0.0

GOST Manager v2.0.0 is the first stable major release. It provides a focused
Direct Mode control plane for official upstream GOST binaries, with local
observability and transactional installation outside the traffic path.

Highlights

  • Stable Direct Mode architecture using the unmodified official
    go-gost/gost release artifact.
  • Independent numbered Iran and Kharej profiles, including multiple Iran
    servers connecting to one Kharej server and multiple independent Kharej
    profiles on one host.
  • Multi-profile create, inspect, edit, clone, selected/all restart, and delete
    workflows with strict profile identity and rollback.
  • Profile-scoped firewall rules with canonical multiple-source support and
    legacy IRAN_IP compatibility.
  • Monitoring Lite for host, network, TCP, storage, services, processes,
    sockets, tunnels, and collector health. Optional conntrack state is reported
    as available, unsupported, or failed without loading kernel modules.
  • An idempotent Server Stability wizard for bounded sysctl settings and exact
    per-profile systemd resource-limit drop-ins without restarting GOST.
  • A safe transactional local installer that validates source, Bash, Python,
    monitoring configuration, and systemd content before committing changes.
  • Public one-command setup.sh installation from checksum-verified GitHub
    Release assets, with pinned-version support and rollback-safe source storage
    at /opt/GOST-Manager.
  • Ubuntu 22.04 and Ubuntu 24.04 support on amd64 and arm64 hosts.

Upgrade Safety

Rerunning the latest setup command upgrades the manager without intentionally
starting, stopping, restarting, or reloading any existing Iran or Kharej
traffic service. Existing tunnel-service PIDs and restart counters are
preserved during a manager-only upgrade. The installer preserves numbered
Direct Mode env files and units, operator-valid monitoring configuration,
SQLite monitoring history, service drop-ins, and managed stability settings.
Monitoring remains optional and is never placed in the traffic path.

Install

Latest stable release:

bash <(curl -fsSL https://raw.githubusercontent.com/WikiPanel/GOST-Manager/main/setup.sh)

Pinned release:

GOST_MANAGER_VERSION=v2.0.0 \
bash <(curl -fsSL https://raw.githubusercontent.com/WikiPanel/GOST-Manager/main/setup.sh)

The setup entrypoint downloads gost-manager.tar.gz and its SHA256 file to a
private directory, verifies and inspects the archive, atomically activates the
verified source at /opt/GOST-Manager, then runs that source's local
transactional installer. The installer verifies the installed VERSION and
manager executable before committing. Setup removes the prior private source
backup only after source and runtime versions are aligned.

Release Validation Sequence

Before merge, validate the exact release/v2.0.0-setup branch on an approved
staging server by cloning it to /opt/GOST-Manager-v2-review and running
bash install.sh --install-dependencies. This Phase A check validates the
local transactional installer and manager upgrade while comparing traffic
PIDs/restart counts, env/unit/drop-in/firewall checksums, monitoring history,
collector health, and active-user continuity. It does not validate the still
unpublished public Release URL, and the production /opt/GOST-Manager source
must not be replaced manually without explicit operator approval.

After setup.sh is merged, the v2.0.0 tag exists, and both release assets
are published, run the public latest setup command on a fresh supported
staging server and one approved existing canary server. This Phase B smoke
repeats the preservation and continuity checks. The public latest-release URL
is a post-release check, not a pre-merge executable blocker.

Product Scope

  • Direct Mode is the only supported traffic mode.
  • There is no NGINX Gateway or Native GOST Gateway.
  • There is no automatic failover controller or hidden routing runtime.
  • The project does not include a custom GOST fork.
  • Monitoring is observational and is not in the traffic path.

This stable release establishes the supported v2 foundation; later releases
may extend the manager while preserving these compatibility and safety
boundaries.