reconD v0.5.0 - Linux Packaging
In case you missed the dev.to's introduction post to reconD, here you go https://dev.to/ercross/recond-pull-based-deployments-for-one-server-without-a-platform-1jjb New in v0.5.0: install it like any other system service Until now, using reconD meant cloning the repo, building it with Go, and writing your own systemd unit. With the new [v0.5.0] release (…
The latest version of reconD, v0.5.0, introduces an easy installation process similar to other system services. Instead of cloning the repository, building with Go, and creating a custom systemd unit, users can now install reconD directly using .deb and .rpm packages for both amd64 and arm64 architectures.
For Debian or Ubuntu systems, users can download the package and checksum file from the releases page and verify the checksum using sha256sum. After installing the package with apt, users should set up the configuration file and enable the service using systemctl. Similarly, on Fedora, RHEL-compatible, or openSUSE systems, the .rpm package can be installed with dnf or zypper, and the service can be enabled and started with the appropriate commands.
The package installs the reconD binary at /usr/bin/recond, includes a systemd unit file, an example configuration file, and a directory for state at /var/lib/recond. The binary itself is renamed to recond. The package is designed to work like a standard system service: it does not start until a configuration is provided, and it prints setup instructions if none are found.
Upgrading to the new release will restart the service, while a downgrade will leave it stopped without affecting existing configuration or state. Uninstallation stops and disables the service while preserving the configuration and state data.
ReconD developers have thoroughly tested the new release through CI, including upgrade scenarios from previous versions. A breaking change is introduced with this release: the default paths for configuration files and state have been changed to lowercase, and the binary name has been updated to recond. Users currently running reconD should follow the migration steps outlined in the changelog to transition to the new format.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.