Financial Assurance Module
  • Financial Assurance Module Documentation
  • INTRODUCTION
    • Glossary / Terminology
    • FAQ
    • Releases / Changelog*
    • Report an Issue / Contact us
  • PRODUCT / END-USER DOCUMENTATION
    • Overview
      • User roles and permissions
    • Financial Assurance Module Navigation
    • Overall User Interface
    • Engagements section
      • Creation of Engagement
      • Reporting of Engagement
      • Submitting of Engagement
      • Finalize the Engagement
      • Export of Engagement
      • Cancellation of Engagement
    • Staff Spot Checks section
    • FAM workflow
  • TECHNICAL DOCUMENTATION
    • Architecture
    • Development Setup
    • Deployment / DevOps
    • Backend Module structure
    • Data Model
    • Fixtures & management commands
    • Integration with permissions framework
    • Interaction with VISION
    • API Documentation
      • Error Handling
    • Frontend
      • Module structure
      • Build process
      • Tests
Powered by GitBook
On this page
  1. TECHNICAL DOCUMENTATION

Deployment / DevOps

PreviousDevelopment SetupNextBackend Module structure

Last updated 6 years ago

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 code has been merged to the develop/master, it is automatically deployed to the staging/production using the following tooling/flow:

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