Ecodev-infra

Purpose

This repo suggests an architecture based on

• Traefik
• PostgreSQL db and pgAdmin interface
• ChromaDB vector store
• MongoDB document database and its associated mongoExpress interface
• Private pypi
• Bookstack and its associated db
• keycloak and traefik forward-auth (to protect apps that cannot implement authentication without keycloak)
• Ofelia
• minio (back and front)
• dozzle
• uptime-kuma
• ElasticSearch

Ecodev infra in a nutshell

Warning

The suggested infrastructure is very basic. It is (in our opinion) only suitable for personal projects and small teams/startups in their infancy. As soon as you have grown enough, you should switch to a managed service approach, being it via cloud giants like AWS, Azure, GCP or with open source managed services. We can for instance highly recommand elestio, thanks to which we discovered Bookstack (that we use) and uptime-kuma (that we enjoyed testing)

Warning

the docker compose files are NOT independant from each other. You MUST make trafik-launch first, then make db-launch. The other compose stacks can be launched (or not) when needed.

For this reason, we strongly advise reading the traefik documentation first, then the db. You can read on the remaining stacks when needed.

Dependencies

Warning

The stacks are not independent. You must

• start the traefik stack first.
• start the db stack second.

• the other stacks can be launched upon need:

• bookstack

• keycloak
• minio
• ofelia
• pypi
• dozzle
• uptime-kuma
• chroma-db
• mongo-db
• elasticsearch

Stack dependencies