Dtella:Configuration Files
This document outlines the files which are to be modified and run by a dtella hub administrator/developer.

dtella.py
—————————————-
Without any command-line arguments, this script will run a local dtella client. The output of which looks like the following:

$ python dtella.py
D - Client Logging Manager Initialized
I - Dtella 1.5.6
I - Listening on 127.0.0.1:7314

Note: the output from dtella.py is broken up into Details, Warnings, and Information (D -, W -, and I -); detailed errors are usually concatenated to the output from python.

Arguments
—————————————-
dtella.py accepts the following command-line arguments:
–port=# (this tells the dtella client to listen on a specific port rather than the default port, 7314).
–terminate (this kills all running instances of dtella.py, including bridges and clients).
–bridge (this initiates the dtella bridge using the configuration file ./dtella/bridge_config.py).
–dconfigpusher (this forces a dynamic configuration update, for information about dconfig read here: [Setting_up_the_Dynamic_Configuration])
–makeprivatekey (this creates a tuple of long integers used in the bridge_config.py file)
–help (this displays all of the dtella.py command-line operations).

local_config.py
—————————————-
This file is parsed during the compilation of your dtella distribution executable. It contains settings which restrict access to the node to specific IP’s/Subnets among other things. See the comments within local_config.py for more details.

bridge_config.py
—————————————-
This file can be found as /dtella/docs/bridge_config.py.example. It should be copied to /dtella/bridge_config.py on the system running the bridge, but otherwise kept as secret as possible.