|
| 1 | +# Why Pulp? |
| 2 | + |
| 3 | +<figure markdown="span"> |
| 4 | + <iframe width="560" height="315" src="https://www.youtube.com/embed/grDXPtnJu4U?si=TPCsysh3GmGAKByY" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> |
| 5 | + <figcaption>If you have to manage hundreds or thousands of packages, Pulp can help!</figcaption> |
| 6 | +</figure> |
| 7 | + |
| 8 | + |
| 9 | +## Selling Points |
| 10 | + |
| 11 | +### Ensure stability and continuity |
| 12 | + |
| 13 | +External content sources can go offline unexpectedly. |
| 14 | +If you want to ensure that you always have what you need, Pulp can help. |
| 15 | + |
| 16 | +### Stop using rsync |
| 17 | + |
| 18 | +Pulp is designed with complex content management workflows and disk optimization in mind. |
| 19 | +If your sync script is letting you down, Pulp can help. |
| 20 | + |
| 21 | +### Reduce rate limiting |
| 22 | + |
| 23 | +From one day to the next, third-party platforms can introduce rate limiting and change the conditions of service. |
| 24 | +If you want to reduce operation costs by having your team consume content from Pulp rather than third parties, Pulp can help. |
| 25 | + |
| 26 | +### Distribute content privately |
| 27 | + |
| 28 | +Sometimes you need a way to distribute private content you have developed in house. |
| 29 | +If you want to keep your private packages off third-party platforms and distribute them internally with ease, Pulp can help. |
| 30 | + |
| 31 | +### Experiment without risk |
| 32 | + |
| 33 | +Every change to content hosted in Pulp creates a new repository version. |
| 34 | +You can rollback to earlier versions whenever you need to. |
| 35 | +If you need to pin packages to certain versions to ensure stability and repeatability, Pulp can help. |
| 36 | + |
| 37 | +### High Availability |
| 38 | + |
| 39 | +Pulp's architecture is designed for both scalability and high availability, offering you the flexibility to scale according to your needs. |
| 40 | +You can boost the capabilities of API request handling, binary/package data serving and tasks processing (e.g, syncing and publishing). |
| 41 | + |
| 42 | +### One tool for different content types |
| 43 | + |
| 44 | +With Pulp, you can fetch, upload, and distribute content from a wide variety of content types. |
| 45 | +Add the plugins for the different content you want to work with and use Pulp to manage them all. |
| 46 | + |
| 47 | +### Safely roll back with repository versioning |
| 48 | + |
| 49 | +Every time you add or remove content, Pulp creates an immutable repository version so that you can roll back to earlier versions and thereby guarantee the safety and stability of your operation. |
| 50 | + |
| 51 | +### Optimizing disk storage and speed during remote synchronization |
| 52 | + |
| 53 | +Download and store only what you need from remote repositories. |
| 54 | +You can select from three modes to optimize disk speed and storage when synchronizing. |
| 55 | +While the default download option downloads all content, you can enable either the on_demand or streamed option. |
| 56 | +The on_demand option saves disk space by downloading and saving only the content that clients request. |
| 57 | +With the streamed option, you download also on client request without saving the content in Pulp. |
| 58 | +This is ideal for synchronizing content, for example, from a nightly repository and saves having to perform a disk clean up at a later stage. |
| 59 | + |
| 60 | +### Multiple storage options |
| 61 | + |
| 62 | +As well as local file storage, Pulp supports a range of cloud storage options, such as Amazon S3 and Azure, to ensure that you can scale to meet the demands of your deployment. |
| 63 | + |
0 commit comments