<commit_before>HOLIDECK
========

The development and simulation tool for [Holiday by MooresCloud](http://holiday.moorescloud.com).

Holideck provies a full simulation environment for Holiday by MooresCloud.
It is functionally identical the behavior of the actual hardware, which
uses the same code base.

Invocation
----------

`% python holideck.py`

When holideck launches it opens two ports on the localhost, one for 
simulator access, the other presenting the web app interface to Holiday. 

The HTML5 simulator simpype will try open port 8888; 
if that port is unavailable, it will increment the port number
until it finds a free port.

IoTAS, the Internet of Things Access Server, will
try to open port 80 (which is only possible if python has been
run with root privleges), or if running as a user program, will 
try to open port 8080.  This port is often occupied by other
applications (Apache, Tomcat, etc), so IoTAS will increment the port
number until it comes to an available port.

All of which is to say that the simulator could be found on port 8888,
but might be at a higher port number, and IoTAS could be found on
port 8080, but could easily be at a higher port number.

The port numbers are given in the output generated by holideck as<commit_msg>Information about holideck.config default port numbers<commit_after>HOLIDECK
========

The development and simulation tool for [Holiday by MooresCloud](http://holiday.moorescloud.com).

Holideck provies a full simulation environment for Holiday by MooresCloud.
It is functionally identical the behavior of the actual hardware, which
uses the same code base.

Invocation
----------

`% python holideck.py`

When holideck launches it opens two ports on the localhost, one for 
simulator access, the other presenting the web app interface to Holiday. 

The HTML5 simulator simpype will try open port number specified
in the configuration file holideck.config. It defaults to port 8888. 
If that port is unavailable, it will increment the port number
until it finds a free port.

IoTAS, the Internet of Things Access Server, will
try to open port 80 (which is only possible if python has been
run with root privleges), or if running as a user program, will 
try to open the port number specified in the configuration file
holideck.config.  It defaults to port 8080. This port is often occupied by other
applications (Apache, Tomcat, etc), so IoTAS will increment the port
number until it comes to an available port.

All of which is to say that the simulator could be found on port 8888,
but might be at a higher port number, and IoTAS could be found on
port 8080, but could easily be at a higher port number. Change the port
numbers in holideck.config if you want the servers to use different ports.

The port numbers are given in the output generated by holideck as
{'fraction_non_alphanumeric': 0.04558303886925795, 'fraction_numerical': 0.01342756183745583, 'mean_word_length': 4.281716417910448, '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': '4896917', 'n_tokens_mistral': 775, 'n_tokens_neox': 719, 'n_words': 448}