Skip to content

v0.8.0

Choose a tag to compare

@github-actions github-actions released this 27 Oct 07:36
· 35 commits to main since this release
Immutable release. Only release title and notes can be modified.
  • MCP --dir scope: a container counts as a scoped server's only through the server's projects in the config or a Compose working directory inside the scope, so a project's supabase/config.toml naming another project's ID no longer exposes that project's containers; a Supabase CLI project ID listed in a server's projects belongs to that server alone, also on the dashboard. Containers and list_ports no longer name a server outside the scope, and ensure_server refuses a dir outside it.
  • Worktree copies: dir must be a worktree git has registered for the repository; a directory whose .git file only points into the repository is refused.
  • MCP: program output quoted by ensure_server and restart_server errors and by container_action is marked as untrusted. The docs say plainly that start and full modes run code the agent can edit.
  • Security, sharing: unpairing a device, or pairing it again, now also refuses its request whose body was still arriving and ends every connection of the old pairing; the body of a paired device's request must arrive within 30 seconds. On Linux the sharing listener accepts connections only from root or your own account, which tailscaled runs as, so other local accounts that read the Serve path cannot send it forged Tailscale headers.
  • Security, sharing: a reply relayed from the connected computer is cut off at 64 MiB, since the daemon may hold a whole reply to sign it for the CLI, so a computer that was taken over cannot exhaust this one's memory.
  • Security, sharing: this daemon never follows a redirect from the connected computer, cuts off a relayed reply that stops for a minute, ignores a state that is not a JSON object, and opens that computer's server addresses only on this computer, at the forwarded port or through the proxy, whatever host they name; the dashboard ignores a state of another shape than it reads.
  • Security: the CLI and the macOS app never follow a redirect from what answers on the daemon's port, for requests and WebSockets alike, which could have sent a signed request elsewhere before its reply was checked; writes need an Origin that is a plain origin (no user, path or query).
  • CLI and MCP: names, notes and commands are printed with control characters replaced in tables, and the list tools tell agents that these fields are data, not instructions.
  • Security, pairing: portside pair <computer> reads the code from standard input (it asks on a terminal, or reads a pipe); the code as an argument, which other accounts could read and redeem first, is refused.
  • Security, forwarded ports: forwarded ports hold at most a quarter of the daemon's open-file limit (about 11,000 ports on a Mac, all of them on Linux), servers first; ports beyond it are listed as over the limit in the Computers window, portside computers and portside doctor, and turning a port off makes room. Binding forwarded ports and checking them for local listeners happen outside the lock other requests wait for, at most 128 every 2 seconds, so thousands of ports no longer stall the dashboard; a local server starting on a port that is being bound gets it, and the dropped bind never forwards a connection. This computer never listens for a forwarded port on the daemon's own, default or fallback ports; such a remote port is listed as busy and can go to another local port.
  • Fixed: starting a server while it is still stopping (portside down and then ensure, or ensure_server and depends_on meanwhile) starts it again once its whole process group has exited, so a child still holding the port does not block it, also when the server exits just as the start arrives or is renamed meanwhile, instead of leaving it stopped until ensure timed out.
  • Fixed: a daemon start after a stop no longer ends a process group whose id another program got in the meantime: a stopping daemon removes its servers' groups from the state once they have exited, and after a crash a leftover group is ended only when its processes can be tied to the server.
  • Fixed: an upgrade in place is refused until a stopping server's processes have all exited, also after its main process did, so the upgrade no longer cuts the stop short and leaves a child running.
  • Fixed: a server that exits while the daemon upgrades in place counts as crashed, so its restart policy or on_crash applies, instead of counting as stopped; with restart = "no" it stays down also when restore brings back the other servers.
  • Fixed: shutting the daemon down while a server stops no longer sends it a second Ctrl-C, which made docker compose abort its graceful stop, and waits until that stop has ended every process the server started, also for a server removed from the config meanwhile; a second portside down also waits for it, and no restart stays announced for a server that crashed just before.
  • Fixed: an on_crash command that leaves a background process holding its output no longer runs forever and takes one of the four slots.
  • Fixed: ready_log and plain logs strip color sequences with : parameters, such as \x1b[4:3m (curly underline), so an anchored ready_log matches.
  • Fixed: a state file that cannot be written (for example a read-only state directory) is reported in the daemon log and as a warning in the dashboard and portside doctor, instead of silently losing which servers you stopped.
  • portside daemon info includes configError also when a running daemon goes on with the last config that loaded.
  • Fixed: turning a server on or off in the config keeps a comment on the enabled line, edits keep the blank lines that end the file, a key written in another case (Enabled) is edited in place, and a server table with two keys that differ only in case (cmd and Cmd) is refused instead of loading either.
  • Linux is a first-class platform (x86-64, arm64), next to macOS: CI runs the systemd user service end to end and an upgrade from the latest release on every change, and the README installs it with the same Homebrew tap (brew install --formula padmk/tap/portside) or from the release archives.

Install

With Homebrew on macOS 26 or later (Apple Silicon), the app and the command:

brew install --cask padmk/tap/portside

On macOS or Linux (x86-64, arm64), the command and dashboard, built from source:

brew install --formula padmk/tap/portside

Portside-0.8.0.zip below is the same app, and the portside_*.tar.gz archives hold the command alone. See the README for details.