**CRTS directory structure** ## bin Control, Controller, Feed, Filter, FilterModules, Thread, buffer files ## development Contains giles related to testing and developing CRTS like interactiveTests, MQTT brokers. Specifically for CRTS developers not for CRTS users. ## include Header files ## lib Contains crts_contestWebServer.js, the main file to run crts. Symlink provided to bin. Scenario controller is node web server. Scenario web server maintains history and passcodes of current scenario only. ## share `share/crts/plugins` contains Controllers and Filters that are used for CRTS. A CRTS user can start developing their own Filter/Controller by looking into these. ## htdocs Default document-root directory for server. Directory holds website related static files that are served up using HTTP_GET through NodeJS server. Keeping this folder outside and not in /var/www/htdocs makes syre that we have a complete encapsulated installation in a single "prefix" directory tree. As a consequence of this strict file structure we can run all the CRTS programs from the source directory without installing it. That saves a lot of development and user time, and makes guessing the path to source files easy. ## Quick Filter Test write a bash script for your filter and test it out without installing crts ## Write your own filter : Guide to CRTS