This page gives an overview of the Admissions Portal, describing its current status, where and how it's developed and deployed, and who is responsible for maintaining it.
This service is currently pre-alpha and is not usable in production.
This service only applies to undergraduate applicants. The Applicant Portal for postgraduates is an unrelated web application.
The Admissions Portal service provides a web application for undergraduate applicants to supply supplementary information as part of their university application, and to track the progress of their university application.
The Admissions Portal is currently pre-alpha.
Technical queries and support should be directed to Dave Hart and will be picked up by a member of the team working on the service. To ensure that you receive a response, always direct requests to Dave Hart rather than reaching out to team members directly.
Issues discovered in the service or new feature requests should be opened as GitLab issues here.
The Admissions Portal is currently deployed to the following environments:
|Name||Public Application URL||Service-to-Service Backend API URL|
The GCP console pages for managing the infrastructure of each component of the deployment are:
|Name||Public Application Static Assets||Public Application Backend||Service-to-Service Backend API|
|Staging||GCP CDN||Firebase||GCP Cloud Run|
|Development||GCP CDN||Firebase||GCP Cloud Run|
All environments share access to a set of secrets stored in the meta-project Secret Manager.
The source code for the Admissions Portal is spread over the following repositories:
|Frontend||The source code for the application frontend|
|Service-to-Service Backend API||The source code for the application service-to-service backend API|
|Infrastructure Deployment||The Terraform infrastructure code for deploying the application to GCP|
The following gives an overview of the technologies the Admissions Portal is built on.
|Service-to-Service Backend API||Python 3.8||FastAPI|
The following gives an overview of how the Admissions Portal is deployed and maintained.
How and where the Admissions Portal is deployed¶
The Admissions Portal infrastucture is deployed using Terraform, with releases of the frontend and service-to-service backend API deployed by the GitLab CD pipelines associated with the infrastructure deployment repository.
Deploying a new release¶
README.md files in each of the source code repositories explain how to deploy the Admissions
GCP Cloud Monitoring is used for tracking the health of applications in the environments and sending alert emails when problems are detected.
- Admissions Portal: High-Level Specification
- Admissions Portal: Backend Specification
- Admissions Portal: Frontend Specification
- Digital Admissions Project Index
Service Management and tech lead¶
The service owner for the Admissions Portal is TBD.
The service manager for the Admissions Portal is TBD.
The tech lead for the Admissions Portal is Dave Hart.
The following engineers have operational experience with the Admissions Portal and are able to respond to support requests or incidents: