THE FIELD GUIDE / START HERE

Enroll your first server

A three-step workflow with independent installation verification.

Mr Patchy documentation · 2 min read

1. Describe the endpoint

Choose Add server. Enter a recognizable name, its hostname or IP address and the SSH port. Targets need systemd, Python 3, OpenSSH server, sudo and OpenSSL. Debian-family targets need dpkg. RPM targets need python3-dnf and python3-rpm; SELinux hosts also need policycoreutils-python-utils.

2. Prepare the target

Download the personalized Bash installer, transfer it to the target and run it with sudo. The offline bootstrap creates /opt/drpatch, the dedicated drpatch account, public-key access, the root-owned bridge and restricted sudo rules. It performs no package downloads or callbacks.

BASH
sudo bash mrpatchy-enroll.sh

Alternatively, select an enabled HTTPS endpoint and use the generated expiring curl link. The generated command downloads into an unpredictable owner-only temporary file and removes it afterward. Private CAs require a trusted CA bundle via curl --cacert. Use the generated command from your own controller.

3. Connect and verify

Verify the ED25519 SHA256 host fingerprint through a trusted console. Enter it and choose Finish and verify installation. Mr Patchy deploys the collector over SSH and verifies hashes, ownership, permissions and service state.

After enrollment

Open the server workspace to check inventory and freshness. Download a fresh installer after SSH-key rotation. Disabling a server suspends future management; deleting a server retains read-only audit history. Removing it from the fleet does not uninstall its remote account or services.

Go deeper

Open the application reference for capability scope and technical details.

Open Open SERVER_WORKSPACES.md on GitHub ↗

Actual application interface with illustrative documentation data.