You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In light of #1679, we should investigate moving TRSS to OpenShift which is our main platform for production applications. It already runs the API and jlink.online. Currently, TRSS is hosted on a EC2 machine at AWS in an ad-hoc fashion.
Investigate whether TRSS can be run on OpenShift. If not, initiate the necessary adjustments.
Ensure TRSS provides endpoints for health checks (indicate whether TRSS is up, MongoDB is operational).
Codify the deployment of OpenShift (Dockerfile, Ansible, ...).
Create staging environment.
Work out backup strategy and implement it.
Create production environment.
Monitor SSL certificate, reachability, health endpoints and resources of TRSS.
The text was updated successfully, but these errors were encountered:
In light of #1679, we should investigate moving TRSS to OpenShift which is our main platform for production applications. It already runs the API and jlink.online. Currently, TRSS is hosted on a EC2 machine at AWS in an ad-hoc fashion.
The text was updated successfully, but these errors were encountered: