Repository navigation
Releases
SVX 1.48.2
- Cleaner self-signed certificates. The generated certificate used to
include the machine's hostname as well as the names you configured — and
inside Docker that hostname is a random container ID, so every certificate
carried a name nobody browses to. The hostname is now added only when no
names are configured inPORTAL_TLS_HOSTNAMES, and never inside a
container.localhostis still always included for the healthcheck. - To regenerate an existing self-signed certificate with the new names, set
PORTAL_TLS_HOSTNAMESin.env, then run
docker compose exec portal python -m tls ensure --forceand
docker compose restart. A certificate you installed yourself is never
touched unless you run that command.
Install (Docker): tar xzf svx-docker.tar.gz && cd svx-*/ && ./install.sh
Install (no Docker): tar xzf svx-native.tar.gz && cd svx-*-native/ && ./install.sh
Upgrade: ./upgrade.sh --bundle svx-docker.tar.gz from your existing install folder.
See the README for requirements and details.
SVX 1.48.1
- The download unpacks to an
svx-<version>folder (and
svx-<version>-nativefor the no-Docker bundle) instead of
fp-f5-ss-<version>. Bundles built here are now
dist/svx-<version>-docker.tar.gzanddist/svx-<version>-native.tar.gz.
The folder stays versioned so that untarring a newer bundle beside an
install never writes over it. - Every bundle starts with a
README.md: what SVX is, what you need, the
three install commands, the first sign-in, the licence in brief, how to
upgrade, and where the full guide is. The no-Docker bundle's
INSTALL-native.mdis nowINSTALL.md, the same as the Docker bundle. - The publish script refuses a bundle without
README.mdandINSTALL.md. - Existing installs are unaffected: the image and its tarball keep their
technical name, soupgrade.sh --bundleworks from any earlier version.
Install (Docker): tar xzf svx-docker.tar.gz && cd svx-*/ && ./install.sh
Install (no Docker): tar xzf svx-native.tar.gz && cd svx-*-native/ && ./install.sh
Upgrade: ./upgrade.sh --bundle svx-docker.tar.gz from your existing install folder.
See the README for requirements and details.
SVX 1.48.0
- Coming soon page, in the app (menu → Coming soon, every role) and on
the website (roadmap.html, linked from the header and footer). It lists
what is planned next:- Standardised Advanced WAF policies — pick an approved WAF template on
the New Virtual Server form; SVX creates a per-app policy, attaches it
with the standard logging profile, in transparent or blocking mode. - BIG-IP DNS (GTM) and GSLB — wide IPs named to the standard, GSLB pools
across data centres from the virtual servers SVX made, and their health
on the dashboard.
- Standardised Advanced WAF policies — pick an approved WAF template on
- The list lives in
ROADMAPinapp.py; a test keeps the website page in
step with it.
Install (Docker): tar xzf svx-docker.tar.gz && cd fp-f5-ss-*/ && ./install.sh
Install (no Docker): tar xzf svx-native.tar.gz && cd fp-f5-ss-*/ && ./install.sh
Upgrade: ./upgrade.sh --bundle svx-docker.tar.gz from your existing install folder.
See the README for requirements and details.
SVX 1.46.0
- New licensing model. SVX is now free for one F5 device and up to ten
virtual servers, with no key. Beyond that you need a licence: a 1-year
or 5-year key, or a trial key that is the full licence for 30 days. - Nothing locks out any more. With no key, or when a key expires or fails
to verify, the portal runs as the Free edition instead of blocking every
page. The automatic 30-day trial clock (data/trial_start.json) is gone;
existing installs without a key become the Free edition on upgrade. - On the Free edition, adding a second device is refused, extra devices
already configured are shown as not licensed and can't be selected or
pushed to, and a request that would make an eleventh virtual server on a
device is refused when it's raised and re-checked when it's pushed. The
dashboard, monitoring and deletions are never limited. - New Licence page (Administration menu) with the edition, expiry, usage
against the limits, the options, and who to contact. It replaces the
licence-expired page; the old URL redirects to it. The top-bar badge links
to it and readsFree,Trial,1-yearor5-year. - The key generator issues
--type trial|annual|5year. - Website, setup guide, public downloads README and install docs describe
the new editions.
Install (Docker): tar xzf svx-docker.tar.gz && cd fp-f5-ss-*/ && ./install.sh
Install (no Docker): tar xzf svx-native.tar.gz && cd fp-f5-ss-*/ && ./install.sh
Upgrade: ./upgrade.sh --bundle svx-docker.tar.gz from your existing install folder.
See the README for requirements and details.
SVX 1.45.0
- SVX can be downloaded from the website. Releases are published to the
public svx-releases repository
(the source stays private), and the website has a Download section with
buttons for the Docker and native bundles. The buttons always fetch the
newest release. The trial buttons on the site now go to the downloads
instead of an email request, since the 30-day trial starts on first run. - New
scripts/publish-public-release.sh <version>publishes a built release:
both bundles under versioned and stable names, a SHA-256 checksum file, and
the changelog notes. It refuses a bundle that contains anything private. - The Docker image no longer includes the release tooling or the website's
CI workflow file.
Install (Docker): tar xzf svx-docker.tar.gz && cd fp-f5-ss-*/ && ./install.sh
Install (no Docker): tar xzf svx-native.tar.gz && cd fp-f5-ss-*/ && ./install.sh
Upgrade: ./upgrade.sh --bundle svx-docker.tar.gz from your existing install folder.
See the README for requirements and details.