<commit_before>forkjs
======

ForkJS is a simple framework which basically lets you easily manage nodeJS processes by forking. Forking is best used for running parallel processes. In NodeJS, forking is also beneficial to fully utilize all the available cores in the system.

To test
----


server.js
------------

server.js will fork processes. This will be the point-of-entry of all fork request. This has control mechanisms which will be helpful to manage the forked process.

Each forked process can represent an app. 

server.js runs an Express HTTP server where it will be accepting commands from Front-end apps.


----

Available commands for server.js:
1. Create
	- This will create an instance of the target nodejs app which accepts a single parameter
	- For this usage, single parameter is sufficient for the nodejs script to run on it's own
	- An app could be connected to database backends, and the parameter could just be an ID of an object
	- Each instance will have it's own ID which comes from the request


2. Run- This will trigger a run command for the instance
3. Stop - This will trigger a stop command for the instance
4. Resume - This will trigger a stop command for the instance
5. Kill - This will trigger a kill command for the instance<commit_msg>FIXED readme<commit_after>forkjs
======

ForkJS is a simple framework which basically lets you easily manage nodeJS processes by forking. Forking is best used for running parallel processes. In NodeJS, forking is also beneficial to fully utilize all the available cores in the system.

To test
----
1. Run server.js on one terminal
	
		-
		node server.js
		-
2. Run tests on another terminal
		
		- 
		node tests/simple.js
		node tests/multiple.js
		node tests/dynamic.js
		-


server.js
------------

server.js will fork processes. This will be the point-of-entry of all fork request. This has control mechanisms which will be helpful to manage the forked process.

Each forked process can represent an app. 

server.js runs an Express HTTP server where it will be accepting commands from Front-end apps.


----

Available commands for server.js:
1. Create
	- This will create an instance of the target nodejs app which accepts a single parameter
	- For this usage, single parameter is sufficient for the nodejs script to run on it's own
	- An app could be connected to database backends, and the parameter could just be an ID of an object
	- Each instance will have it's own ID which comes from the request


2. Run- This will trigger a run command for the instance
3. Stop - This will trigger a stop command for the instance
4. Resume - This will trigger a stop command for the instance
5. Kill - This will trigger a kill command for the instance
{'fraction_non_alphanumeric': 0.05143277002204261, 'fraction_numerical': 0.00440852314474651, 'mean_word_length': 3.4061488673139158, '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': '584271', 'n_tokens_mistral': 704, 'n_tokens_neox': 672, 'n_words': 426}