Debian packages make installation of KeyDB easy. No need to worry about building the binaries, or directory setup. Just simply install and go!
We are now using a single freight repository to serve all Ubuntu and Debian packages. We currently support the following distributions/architectures:
- Debian: stretch (amd64 & arm64), buster (amd64 & arm64)
- Ubuntu: focal (amd64 & arm64), bionic (amd64 & arm64), xenial (amd64)
A PPA (Personal Package Archive) allows you to easily install, update and remove packages with commands such as
dpkg. When you follow the commands below to install KeyDB, the proper package will be selected for your installation. All packages listed in the above section are available through the below method.
In order to get your keydb-ppa, simply follow these commands below:
apt install phase you can choose from several installation methods:
apt install keydb-enterprise-tools to install enterprise binaries only. This method is for someone who wants the program installed but not configured to run automatically (as a service). This package contains keydb enterprise binaries exclusively.
apt install keydb-enterprise-server to run keydb-enterprise-server as a service. Systemd files will be set up as well as directory structures for pid files, conf files, etc. keydb-enterprise-tools is a dependency for this package and will be installed if not already
apt install keydb-enterprise. This installs both keydb-enterprise-server and keydb-enterprise-tools. This is a common installation for most and enables keydb-enterprise features to run with the services configured exclusively for enterprise
For those using keydb-enterprise-sentinel and want to run it as a service you will need to run
apt install keydb-enterprise-sentinel
For those not getting KeyDB DEB packages via the PPA repository, they can be accessed at https://download.keydb.dev/pkg/enterprise/deb/. In this directory listing you can access deb packages for all previous versions as well as the latest versions. For each release there are 4 deb packages available as described above and they are consolidated to their own versioned directory for each release.
In the higher level directories there is a "keydb-enterprise-latest" directory linked to the latest version for ease of access and those running scripts. See above for more information on each deb package.
Unlike with the PPA, you will need to manually install the 'tools' package prior to the others, and you will have to install both 'tools' and 'server' prior to just the 'keydb-enterprise' deb packages.
The directory listing structure narrows down by distribution --> architecture --> keydb --> package
When keydb-enterprise-server is set up as a service you can start, stop and check status via:
This can be done similarly with keydb-sentinel if installed
The main configuration file is located at /etc/keydb/keydb.conf
Other relevant files updated with keydb-enterprise-server are:
Binaries installed with keydb-enterprise-tools are placed in /usr/bin/
By default the service is disabled and will be disabled if your machine is rebooted. If you would like to have KeyDB start on system boot:
If you are running KeyDB as a service with FLASH options enabled, you need to let systemd know you will be accessing the flash volume and make sure the keydb user/group have access. You will need to update the systemd file
/lib/systemd/system/keydb-server.service and append the following line below where the others are located:
This followed by
sudo systemctl daemon-reload
You will then need to change the ownership on the directory of the specified flash volume
Now you should be able to run keydb enterprise with flash as a service and start/stop with
sudo service keydb-server start/stop/status
Choose which package to uninstall based on which packages were installed in the first place. All packages are listed in above command, however some of the packages will remove the packages dependent on them as well.
If you want to remove the ppa from your list of programs to update on
sudo apt update, then remove the .list file in sources:
If you have a build request, issue, or would like to make updates to the packages please email email@example.com