GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing docs.stackstorm.com — Code structure — StackStorm 3.9.0 documentation Code structureYou might be tempted to contribute to StackStorm by this point. Let us walk you through the code a bit. StackStorm/st2 RepoStackStorm is made up of individual services: StackStorm also has a CLI and client library. Code for all these services and components are laid out in different folders in the repo root. st2commonCommon code that contains DB and API data models, utility functions and common service code
that all of StackStorm needs. Each service package (deb/rpm) has a dependency on the st2apiThis folder contains code for API controllers in StackStorm. APIs are versioned and so are controllers.
Experimental controllers are added to st2authContains code for st2actionsContains code for action runners. A new runner written for StackStorm would be added to
Notifier and results tracker are also part of this code base. Notifier is the component that sends notification triggers and action triggers at the end of action execution. Results tracker is an advanced async results querier for certain kind of runners like 3rd party integrations, where execution of an action is kicked off and you have to poll the integrations APIs to collect results. st2clientContains code for both StackStorm client library and StackStorm CLI bundled into one folder. We will eventually split them. st2debugIf you are familiar with st2reactorContains code for both sensor container and rules engine. st2testsShared code containing fixtures and test utilities that helps in unit and integration testing for all StackStorm components. |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |