<commit_before># strongswan chef cookbook

My most important words for you to remember when adjusting any IPSEC configurations are this: 
`"left is local to the machine where the file that you are reading it in resides; right is remote in the same manner"`
SO, on the server side left is local to the server and on the client left is local to that client. Remembering this will save you many a headache when working with VPNs and their setup.

##Overview
=================

I have broken down the installation of the StrongSwan IPSEC daemon into 4 seperate Layers to facilitate the widest range of VPN types. This modular approach makes VPN topologies a little easier to configure and ensures that this process is...
	a) NOT cryptic and 
	b) promotes rampant reuse of code, where possible

This layered approach can be explained thusly:

**Layer One** contains basic connection types; one, and only one, of these will be used for any specific VPN.

**Layer Two** enables a given service and makes it available to the other recipes.
<commit_msg>massaging the markup to match what I originally intended, part deux; again for README.md in the strongswan cookbook<commit_after># strongswan chef cookbook

My most important words for you to remember when adjusting any IPSEC configurations are this: 
`"left is local to the machine where the file that you are reading it in resides; right is remote in the same manner"`
SO, on the server side left is local to the server and on the client left is local to that client. Remembering this will save you many a headache when working with VPNs and their setup.

##Overview
=================

I have broken down the installation of the StrongSwan IPSEC daemon into 4 seperate Layers to facilitate the widest range of VPN types. This modular approach makes VPN topologies a little easier to configure and ensures that this process is...
		a) NOT cryptic and 
		b) promotes rampant reuse of code, where possible

This layered approach can be explained thusly:

**Layer One** contains basic connection types; one, and only one, of these will be used for any specific VPN.

**Layer Two** enables a given service and makes it available to the other recipes.

{'fraction_non_alphanumeric': 0.049726277372262775, 'fraction_numerical': 0.0009124087591240876, 'mean_word_length': 4.468827930174563, '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': '4487293', 'n_tokens_mistral': 546, 'n_tokens_neox': 510, 'n_words': 359}