Hi Brent,

Earlier yesterday Jonathan posted about this on mirror-announce list.

The answer is yes. If you want to host Kitten, you should setup the sync, update your mirror file and submit a PR.

Example, mine from earlier yesterday: https://github.com/AlmaLinux/mirrors/pull/1114

All you have to add is a new section in your mirror config in git (with your UTL of course):

address_optional:

  kitten:
    http: <http URL to a mirror, e.g. http://mirror.cloudpropeller.com/almalinux-kitten>
    https: <https URL to a mirror, e.g. https://mirror.cloudpropeller.com/almalinux-kitten>

    rsync: <rsync URL to a mirror, e.g. rsync://mirror.cloudpropeller.com/almalinux-kitten>

Do note that CI check on your PR may fail as in my case but if you email here Jonathan can manual-merge it until config checker is updated.

Kitten is an optional module that mirror owners can choose to add to their mirrors. Right now it is about 90GB and Jonathan suggested setting aside an additional 500GB-1TB if you choose to mirror it as it will grow with future updates.

Cheers,

Petar Smilajkov
CEO & Chief Architect
Cloud Propeller, Inc.

☁ cloudpropeller.com // web

Sent via Superhuman iOS

On Tue, Oct 22 2024 at 22:56, Brent Kolasinski <b@brentk.io> wrote:

Hi All,

This is a question for the Alma Mirror Team, but probably applicable to everyone wanting to mirror kitten:

With the release of Kitten, I see that there is a new section in the Almalinux Repo file that mirror owners are responsible for forking and PR'ing on git (https://wiki.almalinux.org/Mirrors.html). Should existing mirror owners that choose to mirror Kitten update their repo entry with this new information? I just want to make sure there is no automatic process in place that will conflict with this before putting in a PR for my existing mirror.

Thanks!

./brent

_______________________________________________
Mirror mailing list -- mirror@lists.almalinux.org
To unsubscribe send an email to mirror-leave@lists.almalinux.org