# Pegasus Monitor 1.1.0 (build 2)

## What's new
- Monitor multiple Ubuntu/Debian servers via independent SSH profiles.
- Add, edit, remove and reorder servers; persist profiles locally in macOS UserDefaults.
- Select a server from the menu bar; view its original health groups and diagnostics.
- Consolidated health totals and offline detection; parallel refresh across enabled servers.
- Remote profiles support SSH host aliases, custom key files and individual remote JSON commands.
- New generic read-only Linux health adapter (`server/remote-health-json`).
- Settings and Diagnostics are now **independent windows**, rather than sheets tied to the menu bar window. Editing a field will not dismiss Settings when the menu bar loses focus.
- Retains Pegasus's existing specialised health adapter, application icon, code signing and notarization workflow.

## Install the adapter on another Linux server

Copy `server/remote-health-json` to the remote host, e.g.:

```sh
scp server/remote-health-json USER@HOST:/tmp/pegasus-monitor-health-json
ssh USER@HOST 'sudo install -m 755 /tmp/pegasus-monitor-health-json /usr/local/bin/pegasus-monitor-health-json'
ssh USER@HOST /usr/local/bin/pegasus-monitor-health-json
```

The remote adapter requires Python 3 and built-in utilities; it runs without sudo. Docker checks require appropriate Docker group access; if unavailable they report warning rather than modify permissions.

In Settings → New Server, set the server name, SSH host, username, port and remote command `/usr/local/bin/pegasus-monitor-health-json`. Select Save and Refresh. Configure SSH keys and known_hosts **before** adding the server; interactive password prompts are intentionally disabled.

For Pegasus, the migrated connection continues using `sudo -n /usr/local/bin/pegasus-health-json` and retains its existing 14-group report and 72 checks.

## Notes
- Existing single-server settings migrate automatically on first launch.
- The old preferences are left intact for rollback.
- Profiles do not store passwords or private key contents.
- No remote installations or privileged actions are performed by the Mac app.
- Build and notarize on macOS with Xcode using the existing Scripts directory. The ZIP contains source, not a prebuilt signed application.