<commit_before># LambdaCms Patches

To make the inital setup for a [LambdaCms](http://www.lambdacms.org) website a lot easier, the patches within this repository can be used.
Either clone this repository or copy the required patch file to your machine.

The current patch files are tested with the following Yesod version:

* 1.4.3.3

## Patching all in one

To patch a complete (new) Yesod instance to become a LambdaCms website the file `lambdacms.patch` should be used. Run the following command from with in the Yesod applications root directory (`/path/to` should be replaced with the actual path to the patch file):

```bash
patch -p1 < /path/to/lambdacms.patch
```

Because the name of the `.cabal` file is different for every project the patch command will notice a patched file is missing (we named our `.cabal` `patch.cabal`). When the patch command tries to patch this file you will be prompted for the name of your projects `.cabal` file and you should provide this to successfully finish the patching.

After patching your Yesod project there is one thing left to do. To successfully run the application with `yesod devel` you should edit `config/settings.yml` by uncommenting the last line and inserting a valid email address:

```yaml
#admin: "_env:LAMBDACMS_ADMIN:<your email address>"<commit_msg>Changes tested Yesod version in README<commit_after># LambdaCms Patches

To make the inital setup for a [LambdaCms](http://www.lambdacms.org) website a lot easier, the patches within this repository can be used.
Either clone this repository or copy the required patch file to your machine.

The current patch files are tested with Yesod v1.4.3.3.

## Patching all in one

To patch a complete (new) Yesod instance to become a LambdaCms website the file `lambdacms.patch` should be used. Run the following command from with in the Yesod applications root directory (`/path/to` should be replaced with the actual path to the patch file):

```bash
patch -p1 < /path/to/lambdacms.patch
```

Because the name of the `.cabal` file is different for every project the patch command will notice a patched file is missing (we named our `.cabal` `patch.cabal`). When the patch command tries to patch this file you will be prompted for the name of your projects `.cabal` file and you should provide this to successfully finish the patching.

After patching your Yesod project there is one thing left to do. To successfully run the application with `yesod devel` you should edit `config/settings.yml` by uncommenting the last line and inserting a valid email address:

```yaml
#admin: "_env:LAMBDACMS_ADMIN:<your email address>"
{'fraction_non_alphanumeric': 0.06280928816140084, 'fraction_numerical': 0.003806623524933384, 'mean_word_length': 4.567796610169491, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 2, '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': '547557', 'n_tokens_mistral': 740, 'n_tokens_neox': 718, 'n_words': 393}