No obligation here; offering because we're huge fans of rclone!
More good reasons to use Cloudsmith:
(1) It is free for open-source (and Cloudsmith is happy to foot the bandwidth bill).
(2) Allows @ncw to control the account, in a serverless way, without the hassle.
(3) Allows hosting on a trusted domain such as the official packages site for rclone.
(4) Supports deb, rpm, alpine, and 16 other packaging formats.
(5) Allows division into channels, so stable and beta are not a problem.
(6) Supports proper "any-distro" and "any-version" packages, unlike repropro.
(7) Allows you to bring an official GPG signing key, to establish the provenance of rclone.
(8) Can be managed as an org, so ncw can bring additional collaborators/publishers if he wants.
(9) Supports CI services such as CirceCI, so publishing can happen after a new version is pushed.
(10) You can use "raw" (generic) uploads to support any other type of file hosting in the same place (e.g. macos binaries, windows binaries, etc.)
(11) You can use the API to list the latest versions elsewhere (e.g. your own Downloads page).
There are many more good reasons otherwise people wouldn't pay for the commercial offering.
Pushing looks like this (for Debian, publishing to the rclone account and stable repository):
cloudsmith push deb rclone/stable/any-distro/any-version rclone-v1.51.0-linux-amd64.deb
Using it is similar to the usual:
curl -sLf "https://packages.rclone.org/public/stable/cfg/gpg/gpg.AB12CD34.key" | sudo apt-key add -
sudo add-apt-repository "deb https://packages.rclone.org/public/stable/deb/any-distro any-version main"
sudo apt-get update && apt-get install rclone
If not, I'm otherwise happy to help with advice/setup instead!