VPS Pilotv0.3.0 GitHub

Changelog

Every VPS Pilot release, newest first. Built from CHANGELOG.md in the repository.

  1. v0.3.0

    Release notes and downloads

    Upgrade notes #

    • Upgrading the hub adds the command_runs and command_run_output tables to the operational database on start.
    • Running commands needs agent v0.3.0 or later. Agents from v0.2.x keep working for monitoring and projects, and the dashboard refuses to run commands on them.
    • The agent refuses to run commands from a config.vpspilot.json that is a symlink or writable by its group or others. Ubuntu’s default umask creates files writable by their group, so run chmod 644 config.vpspilot.json on existing configs.

    Added #

    • Run project commands: each command declared in a project’s config.vpspilot.json gets a Run button on the project page. The hub sends only the command’s name; the agent reads the file again, runs the command as the file’s owner in the project directory, and streams its output live to the dashboard. Runs can be cancelled.
    • Run history: every run is recorded with who started it, the command line, the user it ran as, how it ended, its exit code, its duration and its output (up to 4 MiB).
    • Agent --command-timeout (VPS_PILOT_COMMAND_TIMEOUT): seconds a command may run before it is killed. The default is 600.

    Changed #

    • The agent shuts down the same way on SIGTERM as on SIGINT, so a plain kill or docker stop also stops the commands it is running.

  2. v0.2.0

    Release notes and downloads

    Upgrade notes #

    • Upgrading the hub adds a disk_stat table to the timeseries database on start. Agents from v0.1.x keep working and already send disk usage.
    • To move an agent you run by hand to the systemd service, stop it and run curl -fsSL https://vpspilot.dev/install-agent.sh | sudo sh -s -- --hub <hub>:55001. If it used the default state file (/var/lib/vps-pilot-agent/state.json), it keeps its enrollment and needs no token. Otherwise use the command from Re-enroll agent.

    Added #

    • Disk usage: the hub stores the root filesystem’s percent used, the Metrics tab charts it, and alerts can watch it (Disk metric). Agents already sent it, so they don’t need upgrading.
    • Nodes show whether their agent is connected: Online, or Offline with when it was last seen, on the node page and the node list.
    • One-line agent install: Nodes → Add node shows a command that runs https://vpspilot.dev/install-agent.sh. It installs the agent release matching the hub, checks it against SHA256SUMS, sets it up as a systemd service, enrolls it, and removes the token from disk. Running it again upgrades the agent.
    • Agent .deb packages for amd64 and arm64, with the systemd unit.
    • Agent release archives include the systemd unit, vps-pilot-agent.service.

    Changed #

    • The dashboard sidebar shows the VPS Pilot wordmark instead of a placeholder icon and “Enterprise”.

  3. v0.1.1

    Release notes and downloads

    Fixed #

    • Network alerts compare sent traffic with the send threshold and received traffic with the receive threshold. Before, they compared both with an unset field and fired on any traffic. A threshold left empty isn’t checked.
    • Network alert thresholds can be entered in B/s, KB/s or MB/s, and alert cards show them in a readable unit. Before, they had to be typed in bytes per second with no unit shown.
    • Alert cards show whether an alert is enabled. Before, every alert showed as Inactive and the edit form opened with Enabled off, so saving an edit turned the alert off.

  4. v0.1.0

    Release notes and downloads

    Added #

    • Project discovery: the agent finds every config.vpspilot.json under its project directories and reports it to the hub.
    • Per-node scan settings in the dashboard: automatic scan, interval, Rescan now, and the problems from the last scan.
    • Projects added by hand, accepted only inside the agent’s project directories unless it runs with --allow-any-project-path.
    • vps_pilot -version and vps-pilot-agent --version print the release tag, and both log it at startup.
    • Releases include a SHA256SUMS file for checking the downloads.