Package Search Help

You can use boolean logic (e.g. AND/OR/NOT) for complex search queries. For more help and examples, see the search documentation.

Search by package name:
my-package (implicit)
name:my-package (explicit)

Search by package filename:
my-package.ext (implicit)
filename:my-package.ext (explicit)

Search by package tag:
latest (implicit)
tag:latest (explicit)

Search by package version:
1.0.0 (implicit)
version:1.0.0 (explicit)
prerelease:true (prereleases)
prerelease:false (no prereleases)

Search by package architecture:
architecture:x86_64 

Search by package distribution:
distribution:el 

Search by package license:
license:MIT 

Search by package format:
format:deb 

Search by package status:
status:in_progress 

Search by package file checksum:
checksum:5afba 

Search by package security status:
severity:critical 

Search by package vulnerabilities:
vulnerabilities:>1 
vulnerabilities:<1000 

Search by package downloads:
downloads:>8 
downloads:<100 

Search by package type:
type:binary 
type:source 

Search by package size (bytes):
size:>50000 
size:<10000 

Search by dependency name:
dependency:log4j 

Search by uploaded date:
uploaded:>"1 day ago" 
uploaded:<"August 14, 2018 EST" 

Search by entitlement token (identifier):
entitlement:3lKPVJPosCsY 

Search queries for all Maven-specific (and related) package types

Search by group ID:
maven_group_id:org.apache 

Field type modifiers (depending on the type, you can influence behaviour)

For all queries, you can use:
~foo for negation

For string queries, you can use:
^foo to anchor to start of term
foo$ to anchor to end of term
foo*bar for fuzzy matching

For number/date queries, you can use:
>foo for values greater than
>=foo for values greater / equal
<foo for values less than
<=foo for values less / equal

Need a secure and centralised artifact repository to deliver Alpine, Cargo, CocoaPods, Composer, Conan, Conda, CRAN, Dart, Debian, Docker, Go, Helm, LuaRocks, Maven, npm, NuGet, P2, Python, RedHat, Ruby, Terraform, Vagrant, Raw & More packages?

Cloudsmith is the new standard in Package / Artifact Management and Software Distribution.

With support for all major package formats, you can trust us to manage your software supply chain.

Start My Free Trial
 Open-Source tetrate tetrate (Tetrate) / getenvoy-rpm-stable  GitHub Project
getenvoy-rpm: GeteEnvoy RPM Packages
Note: Packages in this repository are licensed as Apache License 2.0 (dependencies may be licensed differently).

Format-Specific Setup

To find out how to get setup locally so you can easily install packages, please select one of the formats from the tabs above.

Please note that the term repository here is Cloudsmith's concept of a package or artefact collection, and should not be confused with other package format specific meanings (such as the term as it is used by Docker, to mean a tagged image).

Note: Only help for package formats that exist in this repository is shown. You can also see the help for all package formats.

Need Help?

If you couldn't find what you needed in our documentation, then you can always chat to a member of our team instead. It's our mission to be your dedicated off-site team for package management, and we mean it. Come and chat with us, anytime.

RedHat logo

RedHat Repository Setup

A repository for RedHat-like systems (such as RHEL, CentOS, SUSE, Fedora, etc.), compatible with yum, dnf, zypper, etc.

The following instructions are for RedHat or compatible packages only.

Distribution Setup

To install packages you'll need to setup your repository, which is specific to your distribution:

To install packages, you can quickly setup the repository automatically (recommended):

curl -1sLf \
  'https://rpm.dl.getenvoy.io/public/setup.rpm.sh' \
  | sudo -E bash

If you need to force a specific distribution, release/version, or even architecture, you can also do that (e.g. if your system is compatible but not identical):

curl -1sLf \
  'https://rpm.dl.getenvoy.io/public/setup.rpm.sh' \
  | sudo -E distro=some-distro codename=some-codename arch=some-arch bash

or ... you can manually configure it yourself before installing packages:

yum install yum-utils pygpgme
rpm --import 'https://rpm.dl.getenvoy.io/public/gpg.CF716AF503183491.key'
curl -1sLf 'https://rpm.dl.getenvoy.io/public/config.rpm.txt?distro=el&codename=7' > /tmp/tetrate-getenvoy-rpm-stable.repo
yum-config-manager --add-repo '/tmp/tetrate-getenvoy-rpm-stable.repo'
yum -q makecache -y --disablerepo='*' --enablerepo='tetrate-getenvoy-rpm-stable'

Note: Please replace el and 7 above with your actual distribution/version and use Wildcards when enabling multiple repos.

To install packages, you can quickly setup the repository automatically (recommended):

curl -1sLf \
  'https://rpm.dl.getenvoy.io/public/setup.rpm.sh' \
  | sudo -E bash

If you need to force a specific distribution, release/version, or even architecture, you can also do that (e.g. if your system is compatible but not identical):

curl -1sLf \
  'https://rpm.dl.getenvoy.io/public/setup.rpm.sh' \
  | sudo -E distro=some-distro codename=some-codename arch=some-arch bash

or ... you can manually configure it yourself before installing packages:

dnf install yum-utils pygpgme
rpm --import 'https://rpm.dl.getenvoy.io/public/gpg.CF716AF503183491.key'
curl -1sLf 'https://rpm.dl.getenvoy.io/public/config.rpm.txt?distro=fedora&codename=29' > /tmp/tetrate-getenvoy-rpm-stable.repo
dnf config-manager --add-repo '/tmp/tetrate-getenvoy-rpm-stable.repo'
dnf -q makecache -y --disablerepo='*' --enablerepo='tetrate-getenvoy-rpm-stable' --enablerepo='tetrate-getenvoy-rpm-stable-source'

Note: Please replace fedora and 29 above with your actual distribution/version.

To install packages, you can quickly setup the repository automatically (recommended):

curl -1sLf \
  'https://rpm.dl.getenvoy.io/public/setup.rpm.sh' \
  | sudo -E bash

If you need to force a specific distribution, release/version, or even architecture, you can also do that (e.g. if your system is compatible but not identical):

curl -1sLf \
  'https://rpm.dl.getenvoy.io/public/setup.rpm.sh' \
  | sudo -E distro=some-distro codename=some-codename arch=some-arch bash

or ... you can manually configure it yourself before installing packages:

microdnf upgrade microdnf # v3.8+ required to use makecache
rpm --import 'https://rpm.dl.getenvoy.io/public/gpg.CF716AF503183491.key'
curl -1sLf 'https://rpm.dl.getenvoy.io/public/config.rpm.txt?distro=almalinux&codename=8.4' > /etc/yum.repos.d/tetrate-getenvoy-rpm-stable.repo
microdnf makecache -y --disablerepo='*' --enablerepo='tetrate-getenvoy-rpm-stable*'

Note: Please replace almalinux and 8.4 above with your actual distribution/version.

To install packages, you can quickly setup the repository automatically (recommended):

curl -1sLf \
  'https://rpm.dl.getenvoy.io/public/setup.rpm.sh' \
  | sudo -E bash

If you need to force a specific distribution, release/version, or even architecture, you can also do that (e.g. if your system is compatible but not identical):

curl -1sLf \
  'https://rpm.dl.getenvoy.io/public/setup.rpm.sh' \
  | sudo -E distro=some-distro codename=some-codename arch=some-arch bash

or ... you can manually configure it yourself before installing packages:

curl -1sLf 'https://rpm.dl.getenvoy.io/public/config.rpm.txt?distro=opensuse&codename=42.2' > /tmp/tetrate-getenvoy-rpm-stable.repo
zypper ar -f '/tmp/tetrate-getenvoy-rpm-stable.repo'
zypper --gpg-auto-import-keys refresh tetrate-getenvoy-rpm-stable tetrate-getenvoy-rpm-stable-source

Note: Please replace opensuse and 42.2 above with your actual distribution/version.

Removing Setup

If you no longer want to install packages from the repository, you can remove it with:

rm /etc/yum.repos.d/tetrate-getenvoy-rpm-stable.repo
rm /etc/yum.repos.d/tetrate-getenvoy-rpm-stable-source.repo
rm /etc/yum.repos.d/tetrate-getenvoy-rpm-stable.repo
rm /etc/yum.repos.d/tetrate-getenvoy-rpm-stable-source.repo
rm /etc/yum.repos.d/tetrate-getenvoy-rpm-stable.repo
zypper rr tetrate-getenvoy-rpm-stable
zypper rr tetrate-getenvoy-rpm-stable-source

Need Help?

If you couldn't find what you needed in our documentation, then you can always chat to a member of our team instead. It's our mission to be your dedicated off-site team for package management, and we mean it. Come and chat with us, anytime.

What's this page? You can always download packages from Cloudsmith manually, but native package manager setup allows you to simplify and automate downloads. A native package manager has intelligence built-in that allows it to understand concepts like metadata, versioning, duplication, convergence, etc. As such, we will always recommend that you install natively where possible. Learn more in the setup documentation.

Top