MCCC Standalone Tool Support Plan

Owned by Mikah Pinegar
Last updated: Jun 16, 2023
2 min read

Introduction

After investigating the current tool architecture and server setup we are recommending the following and would like to get approval from the MCCC.

Challenges with the current architecture

  1. The server has multiple tools that are unrelated on it (WordPress site and Selector tool + Data Entry Tool).

  2. The server is undersized.

  3. There is no version control setup for having a history of the code.

  4. There is no pipeline setup to deploy code from the develop server to the production server.

Proposed solution

  1. We will address the previous challenges and resolve the current bugs in the existing codebase.

  2. The WordPress site will be removed from the server and maintained by a different team.

  3. The develop and production servers will be scaled up and moved to Azure and we will incur the charges.

    1. We will give MCCC the SSH keys and/or access to the resource group in Azure so that you can have control of the data and server if needed.

    2. The original servers can remain up and running or saved as images in Digital Ocean.

  4. We will setup version control using the current GitHub repository and ensure that the code in the repo and on the servers stay in sync.

  5. We will create a pipeline for handling releases from develop to production servers. → ideally triggerable by MCCC.

Fixing the issues identified in the GitHub repo

Once the above is complete we will begin addressing the issues labeled bug in order of decreasing priority in GitHub.

  1. Priority 1 - Emergency

  2. Priority 2 - Fix Soon

  3. Priority 3 Active Mainenance

Will get together with Anna and Juliet to prioritize issues before starting.

Timeline

  1. Setting up the new servers and pipelines → 2-3 weeks.

  2. Fixing the issues listed in GitHub → 3-4 weeks.

  3. Switch DNS to new server → 10 minutes.