Story #5086
Updated by bmbouter over 5 years ago
h3. Problem To allow offline update or installation, as well as "cheap" hosting on a "dumb" http file server, export of pulp distribution is required. Pulp2 has this in the manual https://docs.pulpproject.org/en/2.18/plugins/pulp_rpm/user-guide/recipes.html#export-repositories-and-repository-groups h3. Design In Pulp3 an 'exporter' can send content out of Is this a Pulp system. An exporter named RsyncDistributor should be created that takes the most important option that rsync accepts. Additionally the RsyncDistributor takes either a 'repository' story for pulp_rpm or 'repository_version' but pulp? I'm not both. If 'repository' it will publish the latest repository_version. h3. Implementation Internally it will write the entire repository to a temporary area on-disk and then shell out to rsync. Other ports of rsync-like functionality to Python I don't believe contain the optimization and stability of rsync itself. h3. On Demand Content This feature does not work for on-demand content because the content must be present locally for rsync to ship it to the remote system. sure.
.