Repository navigation
Releases
Releases · darkzmaj/Gobiadactyl-Panel
Gobia Panel 2.0.0
Gobia Panel 2.0.0
First signed Gobia release on the Pterodactyl 2.0 foundation (base commit 240aaf62, 2.0-develop). Built on Linux from commit 858d13324188466a4bff61ec109aa41b1bd082f6.
What is in it
- Pterodactyl 2.0 foundation with the Gobia interface, branding and navigation (instance list with views and categories, live status dots)
- Templates and provisioning, centralized Access (one place to share instances), Hetzner Storage Box backup support (
gobia-backups) - Monaco file workspace, dual server editing, searchable server switcher, cross server file transfers with checksum verification
- Server Settings with a Startup tab, Ports page (old Startup and Network addresses still work)
- Signed one click updates (Admin, Updates) with preflight, database backup, automatic rollback
Files
gobia-panel-2.0.0.tar.gz: the package (production dependencies, built assets and extensions)release.json: the signed manifest the updater verifies (Ed25519)gobia-panel-2.0.0.tar.gz.sha256- Package SHA-256:
49f05b1151a8fe224d9555791787b946e2cc647c74c51d0ee044847cfa16e293 - Signing key (public):
U/2XlTOgdzsn2lebHDxjkh7HFSNqmYLkm+Hj+3MdVJI=(new Gobia 2.0 key; the 1.x key is not used and 1.x installations reject this release)
Verified
- Signature, size and checksum against the committed key; edited manifest, edited checksum, invalid or missing signature, another key, the old 1.x key, tampered and truncated archives are all rejected
- Archive audit: no links, traversal,
.env,.git, tests, tools, mock Wings, keys or tokens - Linux CI (private mirror, all 7 jobs: Static Analysis, Frontend on PHP 8.3 and 8.4, Tests on PHP 8.3 and 8.4 with MariaDB 11 and MySQL 8) green on the release commit
- Disposable Linux install: discovery, preflight, update, automatic rollback of a failed migration and manual rollback worked (
docs/gobia-updater-e2e.md)
Limitations (read before using in production)
- Not tested against real Wings and Docker nodes, PHP-FPM, systemd or the live GitHub API; Hetzner backups not tested on a real Storage Box
- Large file moves above 256 MiB are verified by size, not content hash
- Organisation GitHub Actions were unavailable, so the package was built and signed by hand and CI ran on a private mirror
- Production readiness is not established until the real infrastructure and security checks in
MAJCEK_HANDOFF.mdsections 13 to 16 are done