> For the complete documentation index, see [llms.txt](https://razortheory.gitbook.io/third-party-monitoring-module-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://razortheory.gitbook.io/third-party-monitoring-module-documentation/technical-documentation/untitled-1.md).

# Deployment / DevOps

From a development standpoint we follow the standard git flow doing Pull Requests (PR's) for changes, code review and then merging to develop (the integration branch for testing / staging environments) and master (stable) branches.

Once the code has been merged to the develop/master, it is automatically deployed to the staging/production using the following tooling/flow:

![](https://3736791516-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LJxGPxbbRc1mv-_gOuP%2F-LMMwrhVc4uMg1jeWb0n%2F-LMMxCfQn3JtZnZOey45%2Fassets%252F-LJT531BxmrgZ_gS1UJP%252F-LLTakNG2wAFqr-ZJB7z%252F-LLTaqUSTOgiAuA4APig%252Fdeploy_new.png?alt=media\&token=85cdadda-c04b-4bc1-b6dc-d432b8a5268e)

![](broken://files/-LLTkBwhzhH6GZru8mM8)

CI is done in CircleCI where images are built and tests are run. CircleCI then pushes the various images to the Docker Hub, which is then automatically picked up by the appropriate "stack" in the Docker Cloud.

Periodically during deployment update of core data & permissions is required. For more information please check [related section](/third-party-monitoring-module-documentation/technical-documentation/fixtures-and-management-commands-todo.md).