<commit_before># YumS3Sync

Synchronize a Yum repository over HTTP to S3. This can be useful when you want to mirror Internet Yum repositories 'locally' or want to run the synchronization from within EC2 rather than pushing it from outsede.

There are two command line tools supplied:

yums3sync - Synchronizes a single Yum repository to a bucket:/prefix

yums3syncdir - Scan a directory of links for repositories then synchronize all of them to bucket:/prefix

YumS3sync is smart enough to only copy files changes between runs, and does almost nothing if nothing changed on the source end. 

Syncdir is effectively a wrapper around sync to make it a little easier to synchronize a large amount of repositories without having to know exactly which ones you're synchronizing. I use it to synchronize internal Yum repositories made by other developers to AWS without having to make configuration changes.

After the syncronization you can use the repository using Yum with an S3 plugin or configure a webserver to act as a proxy between S3 and Yum. One of these two options is required if you do not want to make your S3 bucket internet-readable.

## Installation

### Gem<commit_msg>Small readme fixes<commit_after># YumS3Sync

Synchronize a Yum repository over HTTP to S3. This can be useful when you want to mirror Internet Yum repositories 'locally' or want to run the synchronization from within EC2 rather than pushing it from outsede.

There are two command line tools supplied:

yums3sync - Synchronizes a single Yum repository to a bucket:/prefix

* ``yums3syncdir`` Scan a directory of links for repositories then synchronize all of them to bucket:/prefix
* ``YumS3sync`` is smart enough to only copy files changes between runs, and does almost nothing if nothing changed on the source end. 

Syncdir is effectively a wrapper around sync to make it a little easier to synchronize a large amount of repositories without having to know exactly which ones you're synchronizing. I use it to synchronize internal Yum repositories made by other developers to AWS without having to make configuration changes.

After the syncronization you can use the repository using Yum with an S3 plugin or configure a webserver to act as a proxy between S3 and Yum. One of these two options is required if you do not want to make your S3 bucket internet-readable.

## Installation

### Gem
{'fraction_non_alphanumeric': 0.027333894028595457, 'fraction_numerical': 0.007569386038687973, 'mean_word_length': 4.584507042253521, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6211908', 'n_tokens_mistral': 591, 'n_tokens_neox': 563, 'n_words': 375}