Field Monitoring
1.0.0
1.0.0
  • Field Monitoring Module Documentation
  • INTRODUCTION
    • Glossary / Terminology
    • FAQ
    • Report an Issue / Contact us
  • PRODUCT / END-USER DOCUMENTATION
    • Overview
      • User roles and permissions (?)
    • Field Monitoring Module Navigation
    • Overall User Interface
    • Settings section
      • Adding and Editing Questions
      • Sites Management
    • Plan section
      • Building the Rationale For the Monitoring Activity
      • Logging Known Issues
      • Prestructuring Field Monitoring Activities
    • Collect section
      • Activities Overview
      • Drafting a Monitoring Activity
      • Checklist / Questionnaire Setup
      • Checklist Review
      • Assigning / Accepting / Rejecting a Visit
      • Data Collection
      • Report Finalization
      • Submission / Completing a Monitoring Activity
    • Analyze section
      • Monitoring Activity
      • Country Overview
    • FMM workflow (?)
  • TECHNICAL DOCUMENTATION
    • Architecture
    • Development Setup
    • Deployment / DevOps
    • Data Model
    • Fixtures and Management Commands
    • Integration with permissions framework
    • API Documentation
      • Error Handling
    • Frontend
      • Module Structure
      • Build Process
Powered by GitBook
On this page
  1. TECHNICAL DOCUMENTATION

Deployment / DevOps

PreviousDevelopment SetupNextData Model

Last updated 5 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.