Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 4 additions & 0 deletions docs/guides/repositories/pulp_fetch_upload.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,8 @@ $ podman run --detach \

If you browse to `http://localhost:8080/pulp/content/` you should now see "Index of /pulp/content/" that for now is empty, but that you will populate with your repositories by the end of this guide.

![empty_index](images/empty_pulp_index.png)

## Create Pulp Remotes

Think of Pulp remotes as remote source repositories. In this case, the remote source repositories are BaseOS and AppStream from Rocky Linux 9.2 vault. You will use these remotes to sync to your repositories that you will create with Pulp. Please check the [Pulp official documentation](https://pulpproject.org/) for more on remote policies.
Expand Down Expand Up @@ -94,6 +96,8 @@ pulp rpm distribution create --name "Copy of AppStream 92 RL Vault" --base-path

If you check `http://localhost:8080/pulp/content/` you should see your two repositories that are copies of the Rocky Linux 9.2 AppStream and BaseOS vault repositories.

![content_index](images/pulp_index_content.png)

## Conclusion

Pulp can be a very versatile tool used to fetch multiple repositories and distribute them as needed. This is a basic example, however, you can use Pulp in a variety of deployment scenarios and do more complex and advanced repository organization. Please check the [official documentation](https://pulpproject.org/) for more information.