Channels and Beta
If you're after the very latest features or changes, and you know what you're doing - below is how to change from the main release channel, to the Beta channel.
This does mean you're running Beta code, YMMV, and while you can move from Beta back to Main, it's not recommended for everyone. But in a test lab, this could be the place for you.
Debian (Bookworm, Bullseye)
$ cat /etc/apt/sources.list.d/knocknoc.list
deb [signed-by=/etc/apt/keyrings/knocknoc-pub.asc arch=amd64] https://packages.knocknoc.io/debian bookworm beta
#deb [signed-by=/etc/apt/keyrings/knocknoc-pub.asc arch=amd64] https://packages.knocknoc.io/debian bookworm main
Use bullseye in place of bookworm on Debian 11.
Ubuntu (Focal, Jammy, Noble, Oracular)
$ cat /etc/apt/sources.list.d/knocknoc.list
deb [signed-by=/etc/apt/keyrings/knocknoc-pub.asc arch=amd64] https://packages.knocknoc.io/ubuntu jammy beta
#deb [signed-by=/etc/apt/keyrings/knocknoc-pub.asc arch=amd64] https://packages.knocknoc.io/ubuntu jammy main
Ubuntu has its own repository, and the suite is your release’s codename. Run lsb_release -cs if you are not sure which one you are on.
Redhat Distros (Centos, Alma, RHEL etc)
$ cat /etc/yum.repos.d/knocknoc.repo
[knocknoc]
name=Knocknoc Repository
baseurl=https://packages.knocknoc.io/redhat-beta/
#baseurl=https://packages.knocknoc.io/redhat/
enabled=1
gpgcheck=1
gpgkey=https://packages.knocknoc.io/key/knocknoc_public_key.asc
Then update your package lists and upgrade as usual. The commands for each distribution are on Updates and upgrades.