Gobia Panel 2.1.4

Based on Pterodactyl 2.0-develop at 3d93cd07d.

Added

• Panel time zone (Admin, Settings, Extensions, Gobia Core, Time): every time the panel shows (activity, schedules,
  backups, updates, templates) is shown in the chosen IANA zone instead of each browser's, and schedules run at its local
  time, also across daylight saving changes. Stored timestamps stay in APP_TIMEZONE, so changing it is safe at any time.

Gobia Panel 2.1.3

Gobia Panel 2.1.3

Based on Pterodactyl 2.0-develop at 3d93cd07d.

Security

• Templates: "From a server" no longer copies, and following servers are never sent, files that usually hold secrets
  (config/paper-global.yml with the Velocity forwarding secret, forwarding.secret, *.secret, .env). The list is
  secret_files in the gobia-templates configuration.

Gobia Panel 2.1.2

Gobia Panel 2.1.2

Based on Pterodactyl 2.0-develop at 3d93cd07d.

Added

• Following servers (hub sync): a template lists synced paths (Lifecycle tab, for example plugins and config; never
  worlds), and servers created from it can follow it (Instances tab). Each new published revision is rolled out to the
  following servers one at a time: only changed and new files under the synced paths are written and removed ones deleted,
  a running server is restarted and must report running again, and a server that fails gets its previous files back and
  stops the rollout. "Sync now" repeats a rollout. The template is the source of truth; servers never sync with each other.

Fixed

• The browser tab on the sign-in pages showed "Pterodactyl"; it now shows the panel name (Gobia while the name is still
  upstream's default).

Gobia Panel 2.1.1

Based on Pterodactyl 2.0-develop at 3d93cd07d.

Added

• Templates can be created from a live server (Admin, Templates, From a server): software, image, startup, resources,
  variable values and a copy of its files, minus what you leave out. The new template is disabled and unpublished.
• Container installs (GOBIA_UPDATE_RUNNER=image, the default in the release image): the Updates screen reports and verifies
  the next signed release and explains that the update is deploying its image, instead of only saying "not ready".

Security

• A file transfer with resume could overwrite existing files on the destination without file.update; it now needs it.
• Account, Access: granting access is limited to 10 requests a minute (each grant can create accounts and send mail).
• Offsite backups: server users see a generic failure message instead of the storage error, which could name the storage host.
• Account, Access no longer changes shares of suspended servers.

Gobia Panel 2.1.0

Gobia Panel 2.1.0

Upstream Pterodactyl 2.0-develop at 3d93cd07d merged into Gobia, and the Gobia look moved onto the upstream theme platform (gobia-theme). Built on Linux from commit d02a5f24add22cf8eed5077c2bf06934113ff3ba.

What is new

• Upstream 2.0-develop sync (3d93cd0), including its dependency and security updates
• The Gobia look as a theme extension (gobia-theme, activated by the update), with admin customisation of branding, footer, sidebar card and console prompt
• Per person file editor choice: the Gobia Monaco workspace or Legacy (upstream's file pages with the Monaco editor)
• Resource protector: server creation and build edits respect a safe allocation reserve per node; the admin overview shows what is safe to allocate
• Offsite backup scheduler loads each server's node and transfer with the batch (fixes a skipped scheduled backup when several servers exist)
• Container image built only from a signed release package (deploy/docker, see docs/gobia-docker.md)

Upgrading

Direct update from 2.0.0 in Admin, Updates (or php artisan gobia-core:update:run). The release adds 7 migrations; the updater backs up the database first and restores it automatically if the update fails.

Files

• gobia-panel-2.1.0.tar.gz: the package (production dependencies, built assets and extensions)
• release.json: the signed manifest the updater verifies (Ed25519)
• gobia-panel-2.1.0.tar.gz.sha256
• Package SHA-256: 737b69cb0f4d1786afcc6df7090db3885916f9761d479a5d7f04bc06591d330a
• Signing key (public): U/2XlTOgdzsn2lebHDxjkh7HFSNqmYLkm+Hj+3MdVJI= (the Gobia 2.0 key)

Verified

• Linux CI green on the release commit (PHP 8.3 and 8.4, MariaDB 11 and MySQL 8)
• Signature, size and checksum against the committed key; archive audit (no links, .env, .git, tests, keys)
• Updater end to end on Linux: the 2.0.0 package updated to this package (preflight, database backup, migrations, theme, health check); see docs/gobia-updater-e2e.md
• The container image build refuses an edited manifest and a modified archive

The Gobia Release workflow run for this tag failed by design: the signing key is not stored in GitHub, so the package was built and signed by the maintainer on Linux.

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.md sections 13 to 16 are done