Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better documentation for simple mirroring/caching of upstream repos #3500

Open
abctaylor opened this issue Apr 2, 2024 · 4 comments
Open

Comments

@abctaylor
Copy link

Hi, this might be specific to pulp overall, than just the operator.

Could it be documented better (I need help here myself too) how to simply mirror/front some upstream repo? for example, take the Almalinux baseos repo. It has a baseurl (http://almalinux.mirror.katapult.io/8.9/BaseOS/x86_64/os/) and mirrors (https://mirrors.almalinux.org/mirrorlist/8/baseos).

What precisely must be done to provide this on prem via Pulp?

@dkliban
Copy link
Member

dkliban commented Apr 5, 2024

I would recommend filing issues in the pulpcore or pulp_rpm. This issue tracker is specifically for pulp-operator.

Here is a link to the new documentation site that we are working on:

https://staging-docs.pulpproject.org/pulp_rpm/docs/user/tutorials/01-create_sync_publish/

@dkliban
Copy link
Member

dkliban commented Apr 5, 2024

I am going to transfer this issue to pulpcore.

@dkliban dkliban transferred this issue from pulp/pulp-operator Apr 5, 2024
@dkliban dkliban transferred this issue from pulp/pulpcore Apr 9, 2024
@ggainey
Copy link
Contributor

ggainey commented Apr 18, 2024

Note: belongs to RPM since the "interesting" flags/howto are pulp_rpm-specific.

@dralley
Copy link
Contributor

dralley commented Apr 18, 2024

It looks like most of the relevant information is already in our docs page, so I suppose the action item here is to simplify and make it flow better so that this information is more obvious.

@abctaylor @dkliban On that page, do you feel anything in particular is missing or unclear? We definitely want to make sure they're as complete and clear as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants