Fledge v0.1.1 — Pre-release

Fledge v0.1.1 packages the current panel, API, and Linux node agent together under a consistent release version. It also includes the recovery, transfer, retention, enrollment, and verification improvements listed below.

Highlights

• Multi-node registration, one-time Linux agent enrollment, node heartbeats, capacity-aware placement, and durable operations.
• Server lifecycle controls, template-based configuration, collaborator permissions, audit history, and a live console with resource samples.
• SFTP with short-lived per-server credentials and confined server paths. Nodes must explicitly enable the SFTP listener and firewall its port.
• Browser file transfers streamed through object storage up to 1 GiB; the text editor remains limited to 1 MiB.
• S3-compatible backups with retention policies, staged restore, archive integrity checks, and scheduled archive verification.
• Portable Pterodactyl egg conversion, first-admin setup, mandatory administrator two-factor authentication, recovery codes, shared API request throttles, and administrator metrics.
• Fresh-host install scripts and a release updater with health checks and application-code rollback.

Verification

• API TypeScript check, CORS tests, updater tests, and template-converter tests passed.
• Disposable PostgreSQL API smoke suite passed 216 assertions with simulated two-node agent traffic.
• With local S3-compatible storage enabled, the smoke suite passed 226 assertions, including transfer and retention checks. AWS S3 itself was not used.
• Web TypeScript check and production build passed.
• Linux agent Go tests, vet, and build passed under WSL2; optional Docker stdin integration passed against a disposable container.
• Windows installer/updater checks and Linux install, update, connector, and release-artifact checks passed.
• A Minecraft Java server was started on Docker Desktop through the WSL2 agent. Console input, file listing, Docker resource sampling, a 108 MiB backup transfer, and restore succeeded.

Known limits

• Disk allowances are logical guards, not hard filesystem quotas; game processes can exceed them.
• Automatic stateful failover and live migration are not available. Cross-node recovery remains a manual provision, restore, verify, and network-update procedure.
• Backups are archives, not atomic game-consistent snapshots. Verification checks archive readability and safe extraction; it does not boot the game.
• AWS S3, a second physical node, sustained production multi-replica load, and additional game images need deployment-specific validation.
• Docker Desktop on Windows supports local Linux containers and WSL2 Linux-agent evaluation only. Native Windows agents/services and Windows containers are unsupported.
• The agent controls Docker and therefore has root-equivalent authority. Rootless operation and an independent production security review remain outstanding.
• Recovery requires previously saved codes. Application rollback cannot reverse database migrations. External monitoring, load testing, and operational credential rotation need deployment-specific setup.

This is an evaluation pre-release. Keep independent backups and validate restore and network behavior on your own infrastructure before relying on it.