Flytower 1.4.3

Flytower has a new home on GitHub: teamflytower/flytower. From 1.4.3 the panel checks for updates there and the agent downloads them from there. The old address still redirects, so older versions keep updating as before, and nothing changes for your servers. If you keep a copy of the install command, swap MattA-Official/mc-panel for teamflytower/flytower; the old one keeps working.

Testing: update a test box from 1.4.2, check System still lists updates, and run the installer from the new address on a spare VPS.

Features

• set up the organisation board and keep it current in real time (cb97fc2)

Fixes

• only Matt can start the Assistant now the repository has an organisation owner (76428c5)
• board sync follows the repository and the organisation board (06cf205)

Docs

• 1.4.2 notes cover the help and docs screenshots (00d27c7) · #270

Other

• point everything at teamflytower/flytower (dab29bc)

Full diff: v1.4.2...v1.4.3

Flytower 1.4.3-native.1

The native build of 1.4.3. It's the same code as 1.4.3, published so panels on the Native channel move to Flytower's new home on GitHub too: the Rust system helper now downloads updates from teamflytower/flytower. Older native builds keep updating through the old address's redirect.

Testing: update a test box on the Native channel from 1.4.2-native.1 and check the update installs.

Features

• set up the organisation board and keep it current in real time (cb97fc2)

Fixes

• only Matt can start the Assistant now the repository has an organisation owner (76428c5)
• board sync follows the repository and the organisation board (06cf205)

Docs

• 1.4.2 notes cover the help and docs screenshots (00d27c7) · #270

Other

• point everything at teamflytower/flytower (dab29bc)

Full diff: native-1.4.2-native.1...native-1.4.3-native.1

Flytower 1.4.2

Flytower 1.4.2 is a bug-fix and speed update from the same code review as 1.4.1. Scheduled restarts no longer block a backup due during their countdown: the backup runs and the restart waits for it. Stopping the server or changing the task mid-countdown calls the restart off. Live updates no longer arrive twice after the panel reconnects. A stray error can no longer bring the panel down, and the live console follows the log through file events instead of checking it twice a second. The Rust system helper no longer cuts off slow downloads after two minutes.

The Files tab respects view-only access, keeps uploads and edits in the folder they started in, and asks before you leave unsaved changes. Pages that fail to load say so, with Try again, instead of looking empty. Signing in takes you back to the page you wanted. Big imports and logs are capped while they unpack, import links can't be redirected to this machine or its network, and off-site backups tidy up after deleted targets and backups. The public map and Discord /stats show only the players and figures your status page shows, and one huge map no longer holds up every other one. Activity and job history now trim themselves, and database updates are safe for future table changes.

Help is more helpful too. On the website, the docs pages show labelled screenshots of the panel. Inside the panel, Show me goes to the button or setting a help page talks about and lights it up, Do it presses a few safe ones for you (Back up now, Start, Restart, Stop, Copy address) through their usual confirm, and help shows your own details, such as the address players join with.

Re-running the installer now keeps the version you have instead of moving you to the newest stable (add --version latest to move on), copies the database before any downgrade, and the firewall keeps SSH open on whatever port it really uses. Releases now wait for the install and upgrade tests to pass. Testing notes are in each pull request of the 1.4.2 milestone and in #271, #272 and #273.

Features

• docs: live values in help, like your server's address (4eac656) · #270
• docs: Do it in help presses safe controls for you, through their own confirm (0bd8be2) · #270
• docs: screenshot cards on their own, a demo domain, a channel and a public page (ca5fb77) · #270
• docs: anchors for account, content, map, public page, Discord, notifications, branding and disk (4a99625) · #270
• docs: labelled screenshots with numbered pins on the website, Show me in the panel (f53f49f) · #270
• docs: bun run docs:screens takes the labelled screenshots from a demo panel (aaa968a) · #270
• docs: screenshot blocks in the docs, and checks that each one has been taken (c731869) · #270
• panel: Show me follows the page as it loads, and says when a control only shows sometimes (e9ad82e) · #270
• panel: Show me in Help lights up the control a doc names (d6ee3ba) · #270
• docs: :ui chips for panel controls and :shortcut key caps (82057cb) · #270
• panel: mark the controls the docs point at (6978144) · #270
• docs: list the panel controls the docs can point at (5d3d99b) · #270
• site: serve the Worker on flytower.dev (519195a)
• site: use the registered flytower.dev domain (2a4d5ee)
• site: use the shared docs layer for the collection, links and sidebar sections (5e78be2)
• site: list the new Crashes page in the docs sidebar (8c7231c)
• site: legal page route and an analytics opt-out that honours Global Privacy Control (b2614ce)
• site: sponsor and advertise pages, with one-off donations (ff0899f)
• site: changelog from GitHub releases, built at deploy time (3037afa)
• site: first draft of "Why Flytower?" (05ce3e9)
• site: docs from the repo's docs/ folder, with search, contents and an ad slot placeholder (37b29e9)
• site: landing page with the install command and features (ac180b5)
• site: website app on Cloudflare Workers, prerendered, with header, footer and 404 (555ea3f)

Fixes

• docs: bundle the icons the :ui chips show (b8ecd59) · #270
• clear systemd's start count so quick installer re-runs don't trip it (c08a6a5)
• count cleared rows in a way the types allow (8960889)
• tidy off-site copies after target removal, deletes during upload and listings mid-backup (cb75ca1)
• make edits to server.properties and player lists wait their turn (5502d59)
• cap unpacked size of tar imports and check every redirect of an import link (68f6548)
• read tar and cp error output while they run (a4e749c)
• stop unpacking gzipped logs and level.dat files at their size cap (b009bd4)
• quote the architecture when trimming the release file name (3fb0b21)
• keep every Conventional Commit type in the release notes (8664dfd) · #245
• let view-only people open folders and download files (48479de)
• let --version latest move an installed box to the newest stable release (80c3f06)
• keep the installed version on installer re-runs, keep SSH open on its real port, and run nothing from a cut-off download (a272e74)
• clear old activity entries and finished jobs (e0fb27b)
• run migrations with foreign keys off and check references before commit (656f039)
• run map passes per server, a couple at once, and stop a stuck renderer (004f668) · #247
• open only one live-updates socket after the connection drops ([a9e837c](https://github.com/M...

Flytower 1.4.2-native.1

The native build of 1.4.2. It's the same code as 1.4.2, published so panels on the Native channel get its fixes too. For the Rust system helper that means downloads that only stop when they stall rather than after two minutes, Java installs that take turns instead of sharing a folder, a cap on connections, and a fall-back to Bun if it crashes while starting.

Testing: follow Testing the Rust agent on a spare VPS.

Features

• docs: live values in help, like your server's address (4eac656) · #270
• docs: Do it in help presses safe controls for you, through their own confirm (0bd8be2) · #270
• docs: screenshot cards on their own, a demo domain, a channel and a public page (ca5fb77) · #270
• docs: anchors for account, content, map, public page, Discord, notifications, branding and disk (4a99625) · #270
• docs: labelled screenshots with numbered pins on the website, Show me in the panel (f53f49f) · #270
• docs: bun run docs:screens takes the labelled screenshots from a demo panel (aaa968a) · #270
• docs: screenshot blocks in the docs, and checks that each one has been taken (c731869) · #270
• panel: Show me follows the page as it loads, and says when a control only shows sometimes (e9ad82e) · #270
• panel: Show me in Help lights up the control a doc names (d6ee3ba) · #270
• docs: :ui chips for panel controls and :shortcut key caps (82057cb) · #270
• panel: mark the controls the docs point at (6978144) · #270
• docs: list the panel controls the docs can point at (5d3d99b) · #270
• site: serve the Worker on flytower.dev (519195a)
• site: use the registered flytower.dev domain (2a4d5ee)
• site: use the shared docs layer for the collection, links and sidebar sections (5e78be2)
• site: list the new Crashes page in the docs sidebar (8c7231c)
• site: legal page route and an analytics opt-out that honours Global Privacy Control (b2614ce)
• site: sponsor and advertise pages, with one-off donations (ff0899f)
• site: changelog from GitHub releases, built at deploy time (3037afa)
• site: first draft of "Why Flytower?" (05ce3e9)
• site: docs from the repo's docs/ folder, with search, contents and an ad slot placeholder (37b29e9)
• site: landing page with the install command and features (ac180b5)
• site: website app on Cloudflare Workers, prerendered, with header, footer and 404 (555ea3f)

Fixes

• docs: bundle the icons the :ui chips show (b8ecd59) · #270
• clear systemd's start count so quick installer re-runs don't trip it (c08a6a5)
• count cleared rows in a way the types allow (8960889)
• tidy off-site copies after target removal, deletes during upload and listings mid-backup (cb75ca1)
• make edits to server.properties and player lists wait their turn (5502d59)
• cap unpacked size of tar imports and check every redirect of an import link (68f6548)
• read tar and cp error output while they run (a4e749c)
• stop unpacking gzipped logs and level.dat files at their size cap (b009bd4)
• quote the architecture when trimming the release file name (3fb0b21)
• keep every Conventional Commit type in the release notes (8664dfd) · #245
• let view-only people open folders and download files (48479de)
• let --version latest move an installed box to the newest stable release (80c3f06)
• keep the installed version on installer re-runs, keep SSH open on its real port, and run nothing from a cut-off download (a272e74)
• clear old activity entries and finished jobs (e0fb27b)
• run migrations with foreign keys off and check references before commit (656f039)
• run map passes per server, a couple at once, and stop a stuck renderer (004f668) · #247
• open only one live-updates socket after the connection drops (a9e837c) · #237
• return to the page you wanted after signing in (ef833ce)
• forget logins that never joined (10a5a75)
• start a new run after a crash systemd recovered between checks (fbbec16)
• follow the live console through inotify and share one RCON connection (fc4c7be)
• log stray rejections instead of letting them end the panel (2b053b4)
• keep the log tailer running when a read fails (1e9ada1)
• send the rest of an RCON packet when the socket drains (537bd28)
• clear the Rust start marker only after the start-up steps, and document it (8fa3d75)
• treat an empty JAVA_HOME as missing in the Rust agent, like Bun ([99a0766](99a07662d3673df41f418706...

Flytower 1.4.1

Flytower 1.4.1 is a security update, and everyone should install it. It comes out of a full review of the code. It tightens how the panel, the system helper and your servers are kept apart, and the checks behind signing in and permissions. Nothing you use day to day changes.

Each Minecraft server now runs in its own group and can no longer see the system helper or the panel's own data. Servers pick this up the next time they restart. The panel is more careful with files in server folders, which the server itself can change. The system helper keeps its own files where only root can change them, and moves older ones across by itself the first time it starts. Updates run one at a time, and Install won't go to an older version, though Go back to still can. If an update can't save a copy of the database first, it stops and leaves everything as it was. A rollback now only removes files that the new version made.

Sign-in and permissions are stricter too. Discord role mappings and cancelling invites follow the same "no more than you have" rule as roles. Deleting an export or a past world asks for your passkey. Removing a passkey signs out your other devices. Recovery codes and setup tokens are harder to guess. The panel refuses changes that come from other websites. Recovery codes made before 1.4.1 still work, but it's worth making new ones under Account. Testing notes are in testing-1.4.0.md.

Features

• rust-agent: helpers for writing and copying files without following links (51ccd75)
• agent: helpers for writing and copying files without following links (610a2fe)

Fixes

• let the box itself see versions on the health check under Bun (a42cc78)
• rust-agent: move agent state and server archives out of the panel's folder (3faccb8)
• rust-agent: one update at a time, recorded before the updater starts, and no downgrades (13f5560)
• rust-agent: keep database copies root-only and never delete a live file the updater did not save (42d0063)
• agent: clean up database copies in the agent's folder, and serialise with updates (bc45cce)
• agent: move agent state and server archives out of the panel's folder (f0bf531)
• agent: one update at a time, recorded before the updater starts, and no downgrades (b4eca6a)
• agent: keep database copies root-only and never delete a live file the updater did not save (b216eac)
• health check only tells versions to signed-in people and the box itself (62950a4)
• type the export and past world delete calls (42d6105)
• refuse changes from other sites and close the /api/_ gap (20d9f41)
• check lockfile paths before moving or removing content (a07ef8b)
• setup token guesses are limited per address and counted up front (5579a94)
• check the panel's user, not its group, on the Rust agent socket (1be77d0)
• run servers in their own group and hide the agent from them (b799c9e)
• removing a passkey signs out your other devices (0003816)
• past worlds to start a new server from only come from servers you can see (364fa28)
• only follow jobs that exist and that you can see (c593802)
• recovery-code sign-in checks one code instead of every code (d88de71)
• rate limiter forgets old windows and counts the proxy's own hop (4a8a639)
• deleting an export or past world needs a passkey check (8466d05)
• validate level-name and keep world readers inside the server folder (53e098e)
• cancelling an invite needs the standing to have made it (8857b08)
• Discord role mappings follow the no-more-than-you-have rule (6fdd6b4)
• write server-folder files through random exclusive temp files (16841c4)
• only send a saved notification secret back to the same site (36d6b12)

Docs

• release notes for 1.4.1 and its native build (e5de53f)
• where the agent keeps its state, database copies and archives (2fcc26f)
• deleting an export or past world asks for your passkey (fb292d6)
• passkey removal signs out other devices; Discord role mapping limits (3327a12)

Other

• pin version ordering in both agents (33dad60)
• share compareVersions between the panel and the agent (9d2be54)
• check a running server can't see the agent or the panel's data (1793857)

Full diff: v1.4.0...v1.4.1

Flytower 1.4.0

Flytower 1.4.0 gives you finer control over who can do what. The broad permissions are now split into smaller ones. For servers, editing settings, managing content, schedules, community settings and backup schedules are separate, and editing the YAML covers all of them. For Flytower itself, updates, notifications, integrations, branding and SSH are separate. Inviting people and managing roles are no longer the same thing as managing people. Existing roles keep everything they could do before. The role editor groups permissions by area and marks the powerful ones, locks the extras a permission brings with it, and lets you copy any role. People can show exactly what each person is able to do, and a server's Settings has an Access section, so someone with Manage who has access can look after one server's people and invite links without touching the rest.

Chat now goes both ways with Discord. Turn on Chat from Discord on the Discord app card under System, Integrations, then switch it on for a server in its Discord chat settings. Messages in that channel then show in game as [Discord] name: message. This needs Message Content Intent turned on for your app in the Discord Developer Portal, and the bot added to your Discord server with the button on the card. The web map zooms smoothly too: it no longer flashes blank while it zooms or redraws, pinch and trackpad zoom glide, nearby zoom levels load ahead of time, and the map's controls and player markers always stay on top.

The system helper and updater now run the Rust versions by default. If the Rust agent fails to start, Flytower falls back to the Bun one by itself and stays on it until the next update. To choose Bun yourself, put bun in /etc/flytower/agent. Testing notes are in testing-1.4.0.md and Testing the Rust agent.

Features

• chat from Discord switches on the Discord card and server chat card (dacd16f)
• show messages from a server's Discord chat channel in game (8ef16b1)
• keep a Discord Gateway connection with heartbeats, resume and backoff (e4471f7)
• start the Rust agent by default, falling back to Bun if it won't start (ba72ebf)
• Rust agent clears its start marker once listening (5e50170)
• Access section on server Settings (8ca45b1)
• let a server's own access be managed by someone trusted with it (d7a35d4)
• show what each person can do, from all their roles (f80f280)
• role editor grouped by area, with copies and locked extras (8f46f6b)
• say what changed in Activity when roles or access change (4157683)
• group permissions by area and mark the powerful ones (f21526a)
• show and hide panel pages by the finer permissions (b0fdf6f)
• check each part of a spec change against its permission (4c64d2c)
• check the finer permissions on every route (98c135c)
• move custom roles to the finer permissions on upgrade (31ba429)
• split broad permissions into finer keys (bab8d86)

Fixes

• keep map controls above the tiles (aa5d49c)
• keep the chat from Discord badge beside its heading, and name a stop plainly (84ebdef)
• smooth web map zooming (f6bdb7b) · #201

Docs

• release notes for 1.4.0 and its native build (34c8bc8)
• release notes for 1.4.0-beta.2 and its native build (e2cfafa)
• release notes for 1.4.0-beta.1 and its native build (d0f0d03)
• chat from Discord and its testing notes (72a25ce)
• keep the updating page's links inside the docs site (8956ba3)
• Rust agent on by default, and how to choose Bun (5f8e238)
• managing one server's access (50298ab)
• the role editor and what someone can do (ee83ff5)
• drop a testing step that doesn't hold yet (94e21e4)
• testing notes for the finer permissions (d5a56b4)
• describe the finer permissions (b9c1215)

Other

• give the slow RCON command test room for the login (43f02b5)
• clear the agent's start limit between the E2E's quick restarts (545b94f)
• check the Rust agent and its Bun fallback end to end (5ffca21)
• prove nobody gains or loses access in the permission split (a65a42e)

Other changes

• Merge main into feat/permission-split (78b8ece)

Full diff: v1.3.1...v1.4.0

Flytower 1.4.0-beta.2

A small fix for the web map. Since the smooth zooming in 1.4.0-beta.1, the map's tiles could be drawn over its controls, so the top bar, the coordinates and the player markers sometimes disappeared under the map. They now always show on top. Nothing else has changed since 1.4.0-beta.1.

Testing: open a server's map, pan and zoom around, and check the top bar, the zoom buttons, the coordinates, the player list and the player markers stay visible. The rest of the testing notes are in testing-1.4.0.md.

Fixes

• keep map controls above the tiles (aa5d49c)

Docs

• release notes for 1.4.0-beta.2 and its native build (e2cfafa)

Full diff: v1.4.0-beta.1...v1.4.0-beta.2

Flytower 1.4.0-beta.1

The first 1.4.0 beta gives you finer control over who can do what. The broad permissions are now split into smaller ones. For servers, editing settings, managing content, schedules, community settings and backup schedules are separate, and editing the YAML covers all of them. For Flytower itself, updates, notifications, integrations, branding and SSH are separate. Inviting people and managing roles are no longer the same thing as managing people. Existing roles keep everything they could do before. The role editor groups permissions by area and marks the powerful ones. It locks the extras a permission brings with it, and it lets you copy any role. People can now show exactly what each person is able to do. A server's Settings has an Access section, so someone with the new Manage who has access permission can look after one server's people and invite links without touching the rest.

Chat now goes both ways with Discord. Turn on Chat from Discord on the Discord app card under System, Integrations, then switch it on for a server in its Discord chat settings. Messages in that channel then show in game as [Discord] name: message. This needs Message Content Intent turned on for your app in the Discord Developer Portal, and the bot added to your Discord server with the new button on the card. The web map also zooms smoothly now. It no longer flashes blank while it zooms or redraws, pinch and trackpad zoom glide, and nearby zoom levels load ahead of time.

The system helper and updater now run the Rust versions by default. If the Rust agent fails to start, Flytower falls back to the Bun one by itself and stays on it until the next update. To choose Bun yourself, put bun in /etc/flytower/agent. This is a beta, so please try it on a test server first. Testing notes are in testing-1.4.0.md and Testing the Rust agent.

Features

• chat from Discord switches on the Discord card and server chat card (dacd16f)
• show messages from a server's Discord chat channel in game (8ef16b1)
• keep a Discord Gateway connection with heartbeats, resume and backoff (e4471f7)
• start the Rust agent by default, falling back to Bun if it won't start (ba72ebf)
• Rust agent clears its start marker once listening (5e50170)
• Access section on server Settings (8ca45b1)
• let a server's own access be managed by someone trusted with it (d7a35d4)
• show what each person can do, from all their roles (f80f280)
• role editor grouped by area, with copies and locked extras (8f46f6b)
• say what changed in Activity when roles or access change (4157683)
• group permissions by area and mark the powerful ones (f21526a)
• show and hide panel pages by the finer permissions (b0fdf6f)
• check each part of a spec change against its permission (4c64d2c)
• check the finer permissions on every route (98c135c)
• move custom roles to the finer permissions on upgrade (31ba429)
• split broad permissions into finer keys (bab8d86)

Fixes

• keep the chat from Discord badge beside its heading, and name a stop plainly (84ebdef)
• smooth web map zooming (f6bdb7b) · #201

Docs

• release notes for 1.4.0-beta.1 and its native build (d0f0d03)
• chat from Discord and its testing notes (72a25ce)
• keep the updating page's links inside the docs site (8956ba3)
• Rust agent on by default, and how to choose Bun (5f8e238)
• managing one server's access (50298ab)
• the role editor and what someone can do (ee83ff5)
• drop a testing step that doesn't hold yet (94e21e4)
• testing notes for the finer permissions (d5a56b4)
• describe the finer permissions (b9c1215)

Other

• give the slow RCON command test room for the login (43f02b5)
• clear the agent's start limit between the E2E's quick restarts (545b94f)
• check the Rust agent and its Bun fallback end to end (5ffca21)
• prove nobody gains or loses access in the permission split (a65a42e)

Other changes

• Merge main into feat/permission-split (78b8ece)

Full diff: v1.3.1...v1.4.0-beta.1

Flytower 1.4.1-native.1

The native build of 1.4.1. It's the same code as 1.4.1, published so panels on the Native channel get the security fixes too. The Rust system helper gets the same hardening as the Bun one. It only accepts the panel's own user, keeps its files where only root can change them, and makes updates and rollbacks safe.

Testing: follow Testing the Rust agent on a spare VPS.

Features

• rust-agent: helpers for writing and copying files without following links (51ccd75)
• agent: helpers for writing and copying files without following links (610a2fe)

Fixes

• let the box itself see versions on the health check under Bun (a42cc78)
• rust-agent: move agent state and server archives out of the panel's folder (3faccb8)
• rust-agent: one update at a time, recorded before the updater starts, and no downgrades (13f5560)
• rust-agent: keep database copies root-only and never delete a live file the updater did not save (42d0063)
• agent: clean up database copies in the agent's folder, and serialise with updates (bc45cce)
• agent: move agent state and server archives out of the panel's folder (f0bf531)
• agent: one update at a time, recorded before the updater starts, and no downgrades (b4eca6a)
• agent: keep database copies root-only and never delete a live file the updater did not save (b216eac)
• health check only tells versions to signed-in people and the box itself (62950a4)
• type the export and past world delete calls (42d6105)
• refuse changes from other sites and close the /api/_ gap (20d9f41)
• check lockfile paths before moving or removing content (a07ef8b)
• setup token guesses are limited per address and counted up front (5579a94)
• check the panel's user, not its group, on the Rust agent socket (1be77d0)
• run servers in their own group and hide the agent from them (b799c9e)
• removing a passkey signs out your other devices (0003816)
• past worlds to start a new server from only come from servers you can see (364fa28)
• only follow jobs that exist and that you can see (c593802)
• recovery-code sign-in checks one code instead of every code (d88de71)
• rate limiter forgets old windows and counts the proxy's own hop (4a8a639)
• deleting an export or past world needs a passkey check (8466d05)
• validate level-name and keep world readers inside the server folder (53e098e)
• cancelling an invite needs the standing to have made it (8857b08)
• Discord role mappings follow the no-more-than-you-have rule (6fdd6b4)
• write server-folder files through random exclusive temp files (16841c4)
• only send a saved notification secret back to the same site (36d6b12)

Docs

• release notes for 1.4.1 and its native build (e5de53f)
• where the agent keeps its state, database copies and archives (2fcc26f)
• deleting an export or past world asks for your passkey (fb292d6)
• passkey removal signs out other devices; Discord role mapping limits (3327a12)

Other

• pin version ordering in both agents (33dad60)
• share compareVersions between the panel and the agent (9d2be54)
• check a running server can't see the agent or the panel's data (1793857)

Full diff: native-1.4.0-native.1...native-1.4.1-native.1

Flytower 1.4.0-native.1

The native build of 1.4.0. It's the same code as 1.4.0, published so panels on the Native channel get it. The Rust agent and updater are on by default, and the agent falls back to Bun by itself if it can't start.

Testing: follow Testing the Rust agent on a spare VPS.

Docs

• release notes for 1.4.0 and its native build (34c8bc8)

Full diff: native-1.4.0-beta.2.native.1...native-1.4.0-native.1