<commit_before># originator
This will hopefully be a package to help manage Magento modules across projects

# Logic behind the design.
Before 'originator' we used to rsync our modules into the code pool, the main issue is if you delete a file in the
module, it stays in the destination. The --delete flag doesn't work because it tries to delete every file inside
Magento that's not in the original module destination.

## Originator solution

### Using Magento config
Every module in Magento needs a module definition file within the app/etc/modules file. These files are loaded by
Magento in a specific order, Mage_All.xml, Mage_*.xml and the everything else.

The module definition files specify the modules code pool, the modules it depends on and if it's active, it also specifies
in the tab name the module name space and module name. From this we and Magento can extrapolate where this modules code
will be found.

### Single code copy
Chances are if you're a developer you want yo checkout your modules into a single location and use them across multiple
Magento projects. We suggest an absolute or relative path that will be consistent across environments.

### Use GIT
When originator iterates over your projects originator.json file it will check if the module exists, if it doesn't
you'll be prompted about it and the program will exist.<commit_msg>Minor change to the readme.md<commit_after># originator
This will hopefully be a package to help manage Magento modules across projects

# Logic behind the design.
Before 'originator' we used to rsync our modules into the code pool, the main issue is if you delete a file in the
module, it stays in the destination. The --delete flag doesn't work because it tries to delete every file inside
Magento that's not in the original module destination.

## Originator solution

### Single code copy
Chances are if you're a developer you want to checkout your modules into a single location and use them across multiple
Magento projects. We suggest an absolute or relative path that will be consistent across environments.

### Use GIT
When originator iterates over your projects originator.json file it will check if the module exists, if it doesn't
you'll be prompted about it and the program will exist.
{'fraction_non_alphanumeric': 0.036283185840707964, 'fraction_numerical': 0.0, 'mean_word_length': 4.555282555282555, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 2}, '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': '4903631', 'n_tokens_mistral': 539, 'n_tokens_neox': 522, 'n_words': 361}