mareddie / quizae-infrastructure Goto Github PK

With new version of Quizae Backend, I've changed a data layer a bit and adapted MySQL as main storage.

This needs to be reflected in infrastructure as well

Generate keyFile in config directory of mongo. Add there a new user and sync permissions for keyFile. After it's running in stack, initiate rs via mongosh and change replica config (to use container name and port instead of physical address / hostname)

Containers should have at least three restart attempts with condition unless-stopped

There should be two services, Quizae Backend App (try multi-replica setup) - which is a custom image built in Quizae repository, and also Mongo DB container.

Mongo needs to run in Replica Set. Maybe also try to run in multi-container setup for high availability? Do some due diligence.

Secrets (e.g. database credentials) should be managed by Docker Swarm (editable via Portainer).

Backend should be exposed via Traefik, and should be routed on host api.quizae.com.

Database cannot be exposed outside of the cluster. NO PORT FORWARDING.

Research how to use Portainer for CD - CI is done via Github Actions in Quizae repository

There's no need of having server runtime in Swarm, when there's only one node - runtime will be on single server, and having single swarm node doesn't justify the overhead.

Migrate everything on a single docker host setup.