> For the complete documentation index, see [llms.txt](https://docs.trafficmonitor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trafficmonitor.ai/development/dev-environment.md). # Dev Environment The Traffic Monitor software is completely open source, so you are welcome to modify your devices to fit your needs. If you think others will benefit from your changes, you are welcome to [join the community](/help-and-faq/where-can-i-get-support.md) and [contribute back](/development/contributing.md)! The [Traffic Monitor OSS repo](https://github.com/glossyio/traffic-monitor) is set up as a [monorepo](https://en.wikipedia.org/wiki/Monorepo) containing everything to get the TM up and running. ## Node-RED logic [Node-RED](https://nodered.org/) provides the primary logic engine to the Traffic Monitor including: * Accepting input from other applications, such as Frigate for object detection, and sensors such as the radar for speed measurement. * Enriching events by attaching speed * Saving payloads and data internally * Sending data to downstream applications To get started developing: 1. Access the Node-RED interface: `http://:1880` and enter the default username and password. 2. Start a New Project and Clone \[your fork of] the traffic-monitor repo. This will completely reset the current project, so ensure you have saved any changes. 3. Change `flows.json` and `package.json` to the `docker/node-red-tm/data` directory locations so changes will be incorporated 4. Commit changes to the \[forked] repo in a new branch. 5. PR changes following the [Contributing](/development/contributing.md) guidelines. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.trafficmonitor.ai/development/dev-environment.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.