Personal tools

Dtella:Configuration Files

From Dtella Wiki

Jump to: navigation, search

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

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

$ python
D - Client Logging Manager Initialized
I - Dtella 1.5.6
I - Listening on

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

Arguments accepts the following command-line arguments:

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

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 for more details.

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