Future of our Software-Distribution
RPM-Repo & new statistics
Today we have some super important things to discuss with you.
The statistics
The simple and fast stuff first.
The statistics didn't change much, we saw a slight increase in EL usage as normal right now.
Downloads increased by around 10% again.
We don't want to waste your time on statistics if nothing big changed.
The Big News
We want to introduce our own repository to you.
We are now hosting our own rpm-repository for all our official packages and some packages that our developers user personally.
The new repo is hosted at https://repo.setup-tooling.org, the server is hosted in Germany.
You can access the public repo-statistics at Repo-Stats.
Now to the obvious part when doing statistics: What data do we collect on the repo?
We collect the package name that you download, the version, the architecture and client agent, so curl, wget, libdnf (dnf) or browser, and the OS if your client agent pings it to our server.
This data is collected to make our monthly statistics that we publish.
For the move over to our own repo we made this script:
curl -sSL https://repo.setup-tooling.org/scripts/migrate.sh | sudo bash
The script will delete the old COPR repo file and install the new repo file for our official repo.
You can also view the script at the domain in the command.
A note here: We won't publish new updates to the COPR repo, all future updates will happen through our own repo server.
We will issue a last patch to the packages on COPR to notice users of the new repo.
The install scripts will get updated in the coming days as well.
We also added the scripts for the back-end applications to st-community-scripts,
there might still be bugs in that implementation as we needed to patch our implementation afterwards, but that might as well be because of the way we structure our infrastructure.
The build program will write to a db of your choosing for logs, versions, names and all necessary stuff, dbs that are supported by the script are PostgreSQL, Oracle DB, Convex and MySQL/MariaDB.
We recommend running those install scripts on RHEL 10 as that's the only way we tested it.
All code is FOSS as per usual, we are trying to do our best to keep everything we do open to the public and keep everything FOSS.
As a note at the end: This repo change will not impact you that much besides the repo changing.