FleetPilot

[ChristianHandy]

✍️ Description

New script: FleetPilot, a self-hosted operations dashboard for home labs and small companies. It manages servers over SSH and APIs without agents: OS updates, SMART disk health, routers (FRITZ!Box, OpenWrt, OPNsense, pfSense, MikroTik), Proxmox VMs, TrueNAS/Unraid storage, backup servers and fans.

Upstream research (there is no Dockerfile or compose file upstream):

• requirements.txt: Python only, no database server (SQLite). Installed with setup_uv + uv pip install -r; Python 3.13, the Debian 13 default.
• gunicorn.conf.py: the upstream app server config. One worker with threads, because FleetPilot runs background pollers. Binds 127.0.0.1:5000 behind nginx.
• .env.example: SECRET_KEY, DASHBOARD_USERNAME/DASHBOARD_PASSWORD (first admin account, created on first start), FLEETPILOT_DATA_DIR. The production flags (FLEETPILOT_PRODUCTION, _TRUST_PROXY, _COOKIE_SECURE, _HSTS) come from upstream's installer and docs (docs/installation.md).

Choices

• HTTPS through nginx with create_self_signed_cert: FleetPilot sets secure cookies, and WebAuthn security keys need a secure context. Port 80 redirects to 443.
• The admin password comes from random_password in .env. Without it, FleetPilot 1.6 falls back to a weak default.
• An Ed25519 key in /root/.ssh, because FleetPilot signs in to managed servers with it. This is explained in the notes.
• Update: check_for_gh_release, then create_backup of .env, then CLEAN_INSTALL=1 CLEAN_INSTALL_KEEP="data logs venv", restore_backup, setup_uv and uv pip install.

🔗 Related PR / Issue

Upstream: https://github.com/ChristianHandy/FleetPilot. These files are also kept in proxmox/community-scripts/ there.

✅ Prerequisites (X in brackets)

• Self-review completed – Code follows project standards.
• Tested thoroughly – Changes work as expected.
• No breaking changes – Existing functionality remains intact.
• No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

---

🏗️ arm64 Support (X in brackets)

• arm64 supported - Tested and supported on arm64.
• arm64 not tested - Assumed to work on arm64, but testing has not been done.
• arm64 not supported - Confirmed upstream dependencies or binaries do not support arm64.

var_arm64 is left commented out, so users are asked. FleetPilot is pure Python with no prebuilt binaries, but this script has not been run on arm64.

---

🖥️ Tested on (X in brackets)

• Proxmox VE – Created on a Proxmox VE host and the app works.
• Incus – Created on an Incus host and the app works.

Tested on Proxmox VE 9.2.20 (kernel 7.0.14) with the current core engine. The files were loaded locally with COMMUNITY_SCRIPTS_ROOT, using mode=default and DIAGNOSTICS=no.

• Install (release v1.6.0): the run completes. HTTPS answers and HTTP redirects to HTTPS. Sign-in with the generated password works. A crawl of all 107 GET pages as admin returned 0 server errors.
• Update: run inside the container, it correctly reports "No update available". With ~/.fleetpilot set back to 1.5.3, a full update stopped the service, backed up .env, deployed the release, restored .env (same checksum) and kept data/ (users intact). The service came back up.
• Upstream main (the coming 1.7.0, deployed from the branch in a separate run): installs and passes the same crawl.

---

🛠️ Type of Change (X in brackets)

• 🐞 Bug fix – Resolves an issue without breaking functionality.
• ✨ New feature – Adds new, non-breaking functionality.
• 💥 Breaking change – Alters existing functionality in a way that may require updates.
• 🆕 New script – A fully functional and tested script or script set.
• 🌍 Website update – Changes to website-related JSON files or metadata.
• 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
• 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

---

🔍 Code & Security Review (X in brackets)

• Follows CODE-AUDIT.md & CONTRIBUTING.md guidelines
• Uses correct script structure (AppName.sh, AppName-install.sh, AppName.json)
• No hardcoded credentials
• No Docker / Docker Compose – The application is installed bare-metal; Docker is not used.
• No git pull – Updates use fetch_and_deploy_gh_release, fetch_and_deploy_codeberg_release, fetch_and_deploy_gl_release, or fetch_and_deploy_from_url instead of git pull.

---

🤖 AI Assistance (X in brackets)

• No AI used – Scripts were written without AI assistance.
• AI was used – I confirm the scripts were built using AGENTS.md and .github/agents/pve-script-creator.agent.md as guidance, and the output has been reviewed and corrected to match those guidelines.

LLM use: Claude Opus 5.5 (Claude Code, low reasoning-effort setting) wrote the ct, install and json files following AGENTS.md. It checked them against the checklist and tested install and update on the author's Proxmox VE 9.2 host, as described above.

---

📋 Additional Information (optional)

• No helper functions of our own, no useradd/runuser, no apt-get, every msg block is balanced, and the footer is motd_ssh/customize/cleanup_lxc. shellcheck is clean at warning level, apart from engine-provided variables.
• The in-app "FleetPilot update" page expects a git checkout. A JSON note points users to this script's update function instead.
• Category 9 (Monitoring & Analytics).

---

📦 Application Requirements (for new scripts)

⚠️ Do not remove this section.
It is used by automated PR validation checks.
If this PR is not a new script submission, leave the checkboxes unchecked.

Required for 🆕 New script submissions.
Pull requests that do not meet these requirements may be closed without review.

• The application is at least 6 months old
• The application is actively maintained
• The application has 600+ GitHub stars
• Official release tarballs are published
• I understand that not all scripts will be accepted due to various reasons and criteria by the community-scripts ORG

FleetPilot does not have 600 stars yet (it was created 2026-01-03). Feel free to close this PR if that rules it out; the scripts will stay maintained upstream in the meantime.

🌐 Source

• Repository: https://github.com/ChristianHandy/FleetPilot
• Releases: https://github.com/ChristianHandy/FleetPilot/releases
• Installation guide: https://github.com/ChristianHandy/FleetPilot/blob/main/docs/installation.md

[github-actions]

Try this script

ct/fleetpilot.sh, run in the Proxmox VE shell or on an Incus host:

COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/ChristianHandy/DevScripts/feat/fleetpilot \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/ChristianHandy/DevScripts/feat/fleetpilot/ct/fleetpilot.sh)"

COMMUNITY_SCRIPTS_URL is not optional for ct/. Fetching the ct/ script from a
branch does not tell the engine where that branch is — with bash -c "$(curl …)"
there is no file on disk for the scripts root to be derived from, so it would fall
back to upstream main and look for the install script there.

Against a core branch as well

Add COMMUNITY_SCRIPTS_CORE_URL=https://raw.githubusercontent.com/OWNER/core/BRANCH
to test an engine change at the same time. The two resolve independently.

Useful flags while testing

dev_mode=net logs every fetch with status and duration, so you can confirm the
branch is really being used. dev_mode=keep stops a failed build from deleting
the container along with the evidence.

[github-actions]

⚠️ Not ready for review yet

@ChristianHandy, this pull request is missing the following:

• The application has 600+ GitHub stars

Edit the PR description to fix it — no new PR needed. This check runs again on every edit and clears itself once everything is in place.

Until then the PR is marked stale and will be closed in 7 days.

---

@community-scripts/contributor please take a look: close it, comment, or set keep-open to keep it.

[ChristianHandy]

Thanks for the automated checks. I know FleetPilot doesn't meet the 600-star requirement yet, and I've left that box unchecked on purpose.

If you're open to it, could a maintainer set keep-open so the scripts can be tested and reviewed in the meantime? The scripts follow AGENTS.md. I tested install and a real update (1.6.0 → 1.7.0) on Proxmox VE 9.2, and upstream now publishes clean release tarballs for every version.

If the star requirement rules it out, closing this is completely fine; I'll resubmit once FleetPilot qualifies.

[asylumexp]

Suggested change

# FleetPilot signs in to the servers it manages with this key.

[asylumexp]

Suggested change

	"text": "Open https://<container-ip> and accept the self-signed certificate once. Sign in as admin; the password is DASHBOARD_PASSWORD in /opt/fleetpilot/.env. Change it after the first sign-in under My Profile and set up two-factor sign-in.",
	"text": "The dashboard password is auto-generated and is saved as DASHBOARD_PASSWORD in /opt/fleetpilot/.env.",

[asylumexp]

Suggested change

	"text": "FleetPilot manages other machines over SSH with the key /root/.ssh/id_ed25519.pub inside the container. Add that key to each server's authorized_keys, or use Manage Hosts → Install Key. To manage the Proxmox node itself, add the node as a host the same way.",
	"text": "FleetPilot manages other machines over SSH with the key /root/.ssh/id_ed25519.pub inside the container. Add that key to each server's authorized_keys, or use Manage Hosts → Install Key.",

[asylumexp]

Suggested change

	},
	{
	"text": "Update FleetPilot with this script's update function. The in-app 'FleetPilot update' page expects a git checkout and does not apply to this container.",
	"type": "warning"
	}
	}

[asylumexp]

I've just realised the parent repository does not have 600 GitHub stars. Sorry this does not meet our requirements for merging into our repository.