Platform Guide | Get Ahed Platform

Introduction

This page documents the Get Ahed platform architecture.

Platform

The platform can be broken into 3 parts:

• Project API, the brain of the project
• The Web App, the user facing part of the project
• SCORM API, a small server which serves and manages the SCORM content All 3 parts are hosted on a Digital Ocean server.

The API (CMS)

The API is a Directus application with a colocated database. Admin users should be the only users interacting with this part of the platform.

All data for the web app can be edited here, including page, images and assessment questions and feedback. For more details on how to change this data please review the how to guide

The Web Application

The web application is what the users see, it handles all interaction using statically rendered web pages and collects data from the API (directus application) or the SCORM API (when viewing a training)

SCORM API

The SCORM API is a standalone web server that serves the SCORM content. Directus is not able to render the content itself, so the SCORM API serves the necessary files when the web app looks for training courses that feature SCORM content.

Other Software

The other software employed by the platform are more standard pieces:

• DNS: Cloudflare is used to route traffic to the web application
• Emails: Mailgun is used to send the password reset emails
• Status: UptimeRobot solution, The API and web application are monitored every minute to ensure they remain online.

** Please note that if mailgun exceeds 100 emails a day, there will be a monthly charge. For now the account just fails to send the mail over 100 per day.