github sctg-development/sctgdesk-server sctg-v1.1.16-sctg.8

49 minutes ago

This release is about where the server runs and how it is installed: hbbs and hbbr
become real Windows services with a winget package, the Linux packages gain armv7, OpenWrt routers get apk packages
(including MIPS), and the packages are served from signed apt, rpm and apk repositories on GitHub Pages.

Windows

  • Windows services: started with --windows-service, hbbs and hbbr talk to the service manager, move to
    %ProgramData%\SCTGDesk (or SCTGDESK_DATA_DIR), log to files rotated at 10 MB (5 kept) and stop cleanly. The
    services are declared with sc.exe, there is no installer; see docs/windows.md.
  • winget: the package SCTG.SCTGDeskServer is available (winget install SCTG.SCTGDeskServer --scope machine) and
    winget.yml opens the pull request to microsoft/winget-pkgs when a full release is published. Each release now
    carries a flat sctgdesk-server-<version>-winget-<x86_64|aarch64>.zip next to the usual archive, so that the winget
    manifests do not have to be rewritten by hand.

Linux packages

  • armv7 (32-bit hard float): deb and rpm for armv7-unknown-linux-musleabihf, cross-compiled with
    cargo-zigbuild and tested under QEMU in the CI.
  • OpenWrt apk packages for hbbs, hbbr and rustdesk-utils, with a procd service and a UCI configuration
    file per program (/etc/config/sctgdesk-hbbs, /etc/config/sctgdesk-hbbr), for:
    • x86_64
    • aarch64_generic, aarch64_cortex-a53, aarch64_cortex-a72, aarch64_cortex-a76
    • arm_cortex-a7_neon-vfpv4, arm_cortex-a7_vfpv4, arm_cortex-a9, arm_cortex-a15_neon-vfpv4
    • MIPS: mips_24kc, mips_4kec (ath79, big endian) and mipsel_24kc, mipsel_74kc (ramips, little endian)
  • The apk packages are installed for real on Alpine in the CI, and the MIPS builds are started under QEMU against the
    API.
  • apk versions are numbers only, so 1.1.16-sctg.8 is published as 1.1.16.8 (which still sorts after
    1.1.16.7).

Package repositories

The packages are now also installable from signed repositories published on GitHub Pages, next to the manual:

Repository Address For
apt https://sctg-development.github.io/sctgdesk-server/apt Debian, Ubuntu (amd64, arm64, armhf)
rpm https://sctg-development.github.io/sctgdesk-server/rpm Fedora, RHEL and clones, openSUSE (x86_64, aarch64, armv7hl)
apk https://sctg-development.github.io/sctgdesk-server/apk/<architecture> OpenWrt 25.12+ and Alpine

Only the latest full releases are kept (no pre-releases). The apt and rpm repositories are GPG-signed (the signature
covers the metadata, hence repo_gpgcheck=1 and gpgcheck=0), the apk repository uses an RSA key. The installation
commands and the architecture table are in docs/repositories.md.

pages.yml replaces docs.yml: the manual and the repositories are deployed together when a release is published.

Docs and CI

  • New pages: docs/windows.md (services, firewall, file locations, removal) and
    docs/repositories.md (repository use, signing keys, how to rebuild them); the README documents
    the repositories, OpenWrt, armv7 and the Windows service.
  • packages.yml is renamed Linux packages (deb, rpm, OpenWrt apk) and builds, packs and installs every architecture
    it publishes, armv7 under QEMU included.
  • build.rs handles its temporary directory across the cross-compilation platforms.

For maintainers

The new jobs need three secrets: REPO_GPG_PRIVATE_KEY (and REPO_GPG_PASSPHRASE if the key has one),
REPO_APK_PRIVATE_KEY and WINGET_TOKEN (classic token, public_repo, on the account that owns the fork of
winget-pkgs). Without them the repositories and the winget pull request are not published; the release files are.

Upgrade notes

  • Nothing to change for an existing deployment: the data directory, the CLI options and the Docker image are the same.
  • On Windows, the service must be created once with sc.exe (see the documentation). The data moves to
    %ProgramData%\SCTGDesk unless SCTGDESK_DATA_DIR points elsewhere: copy the key pair and the database there.
  • On OpenWrt, apk and OpenWrt 25.12 or later are required. Older releases (opkg) are not supported: use the static
    binary from the releases.

Caveats: the MIPS builds run in the CI but have not been tried on a real router; please report what you see. The
Windows binaries are not code-signed, so SmartScreen or an antivirus may warn on the first run.

Don't miss a new sctgdesk-server release

NewReleases is sending notifications on new releases.