Releases: dfagundez/portify
Releases · dfagundez/portify
Release list
v0.1.0
First release of the Rust rewrite. A CLI and a tray app over one shared core: see every port in use, and free one with a single command or a click.
$ portify kill 3000
✔ port 3000 freed: node (PID 12841) terminatedWhich file do I want?
| Platform | Download |
|---|---|
| Windows | Portify_0.1.0_x64-setup.exe — installs for your user, no admin needed |
| Windows (managed fleets) | Portify_0.1.0_x64_en-US.msi — for Intune, SCCM or group policy |
| macOS (Apple silicon) | Portify_0.1.0_aarch64.dmg |
| macOS (Intel) | Portify_0.1.0_x64.dmg |
| Linux (Debian/Ubuntu) | Portify_0.1.0_amd64.deb |
| Linux (anything else) | Portify_0.1.0_amd64.AppImage |
| CLI only | portify-cli-* — one binary, ~950 KB, no runtime |
The desktop app bundles the CLI's engine but not the portify command; grab the CLI archive too if you want both.
These installers are not signed
Your operating system cannot verify who published them, so it will warn you:
- Windows — SmartScreen shows "Windows protected your PC". Choose More info → Run anyway.
- macOS — Gatekeeper blocks the app. Open System Settings → Privacy & Security and choose Open anyway.
Signing needs a certificate, tracked in #4.
Worth knowing
- Portify only sees the OS it runs in. On Windows, WSL services appear as
wslrelay.exe— the forwarding bridge, not the process inside Linux. Install the CLI in your distribution too if you work there. See the README. - Ports whose owner the OS hides show as
(hidden). Run elevated to see and kill them. - Before killing, Portify tells you what else the target process is holding. One WSL relay can front dozens of ports at once.
Status
Verified by hand on Windows 11. macOS and Linux share the same code paths and pass CI, but nobody has run the desktop app on a Mac yet — reports welcome.
Full detail in CHANGELOG.md.