AOSSIE-Org / AOSSIE-Org/EduAid

[FEATURE]: Deployment Strategy Discussion

Abierto
#528 2 comentarios 0 reacciones 0 asignados Ver en GitHub
enhancement
Lenguaje dominante
JavaScript
Estrellas
171
Forks
423
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### Feature and its Use Cases

Hi @yatikakain @Aditya062003 ,

I noticed that the project currently does not have an automated deployment setup.
All components (backend, web app, extension, desktop) appear to require manual local setup.

I wanted to get guidance on the preferred approach.

- Should we use **GitHub Actions** for automated build and deployment workflows?
- Docker Suggestion (For Development)

I was thinking Docker could be useful mainly for **standardizing the development environment** and ensuring the backend server starts consistently across systems.

Docker Benefits for EduAid:
1. Solves Dependency Hell
``` bash
# Current: 34 Python packages + Node.js + System deps
# Docker: One container, all dependencies locked
```
2. Handles Large Models Perfectly
Model Caching: Docker layers cache ML models
Consistent Environment: Same PyTorch/CUDA versions
Storage Management: Persistent volumes for models
3. Multi-Service Architecture
```yaml
services:
backend: # Flask + ML models
web-app: # React frontend
nginx: # Reverse proxy
redis: # Optional caching
```
4. Deployment Scenarios
Development:
```bash
docker-compose up
vs
# Current: 30+ manual setup steps
```

### Additional Context

_No response_

### Code of Conduct

- [x] I have joined the [Discord server](https://discord.gg/hjUhu33uAn) and will post updates there
- [x] I have searched existing issues to avoid duplicates

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.