Private RPM repository fast and easy
RPM packages and RPM package managers like YUM or DNF are essential for development teams working on Linux-based operating systems such as Red Hat, CentOS, Fedora, Oracle Linux, SUSE, openSUSE, Scientific Linux and others.
RpmDeb is a fully managed cloud package repository service that is compatible with RPM package managers such as YUM or DNF, and supports the RPM format. RpmDeb allows creating your private cloud package RPM repositories to store and process RPM packages used by your development and operation teams. No coding, installation or maintenance is required.
Rpm private cloud repository is a must-have when:
Your projects are completed by distributed teams using the same packages from different locations.
Your project requires utilizing private packages.
The dependence on accessibility of public repositories may hinder development and distribution workflows.
All of RpmDeb plans allow to create unlimited number of private repositories and to invite unlimited number of collaborators. Our major focus is on high availability, accessibility, security and safety of your components.
What is more? RpmDeb is stable, fast, and it also serves to host private Debian, NPM, and Maven repositories (coming soon).
Three simple steps to start storing RPM packages.
Step 1 - Register an Account with RpmDeb
Register a new RpmDeb account here. Enter your TEAM_NAME, Email and Password and confirm your account by clicking the link in the email we’ll sent to the specified email address.
Step 2 - Create a Repository
Login to RpmDeb Control Panel and create a repository. You need to set REPOSITORY_NAME and its privacy level: public or private.
If your repository is public, anyone can install packages from it. To install packages from private repository, one will have to use a token. To add and update packages, the use of tokens is required both for private and public repository.
You can access you repository via the link (do not forget to substitute
your team and repository names):
Step 3 - Create a Token
Tokens are randomly created 32-byte strings. Additionally they can have properties like Name, Description and Access level. The access level can be: PULL (enables installing packages from the repository), PUSH (enables adding new or updating existing packages), or both at the same time.
Note: Tokens are team-level objects. This means that a token can be used to access all repositories within the team for which it was created. If you need to be more specific in terms of access control, you can always create a new team and the tokens for the team. With RpmDeb a single account can have as many teams as necessary.
Uploading RPM Packages to RpmDeb Repository
You can upload a package to RpmDeb via Control Panel, or by using a cURL with the following command (mind the corresponding placeholders):
$ curl -F package=@path/to/you/package.rpm -u "TOKEN" https://put.rpmdeb.com/TEAM_NAME/REPOSITORY_NAME/
You will see your packages appear in the RpmDeb Control Panel.
Installing RPM Packages from RpmDeb Repository
To install RPM packages from your repository, first create a
repository configuration file in the
/etc/yum.repos.d/ directory, using
the following sample template defining
[my-repo] name=My RpmDeb Private Repository baseurl=https://TOKEN@rpm.rpmdeb.com/TEAM_NAME/REPOSITORY_NAME/ enabled=1 gpgcheck=0 repo_gpgcheck=1 gpgkey=https://rpm.rpmdeb.com/TEAM_NAME/REPOSITORY_NAME/pub.gpg.key
Note: Please refer to the Documentation for the list of available options and their values.
List the packages in the
rpmdeb repository with:
$ yum --enablerepo=my-repo --disablerepo=* list available
and install them:
$ yum -y install package-name-here