feat(runtime): lean dev profiles and remote/shared heavy services so the stack runs on modest machines

Abierto
#135 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust, yaml

Línea de trabajo

This is design-scale work touching config parsing, the atlas dev orchestrator and service supervision. Start by reading how atlas.yaml is parsed into service definitions and where atlas dev starts and tracks processes, then look at the existing status/logs plumbing that a remote service would have to reuse. Done means atlas dev --profile store boots only that subset, a remote: service is tunnelled and appears in status/logs like a local one, and profile RAM estimates are reported from measured history.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

Running the full stack locally (DB, Redis, API, worker, 3 web apps, SSR store, AI runtime, video studio) needs a high-end machine. Most tasks touch 2–3 services. Teams should be able to develop on modest laptops.

Proposal

  • profiles: in atlas.yaml (e.g. core, store, ai, full) and atlas dev --profile store; services outside the profile stay stopped but startable on demand.
  • Lazy start: a stopped dependency starts on first request to its port (socket activation style) and stops after idle.
  • Remote services: mark heavy services (DB, AI runtime, studio) as remote: <host> so atlas tunnels the port instead of running it locally; health and logs still visible.
  • Report estimated RAM per profile from measured history.

Acceptance

  • atlas dev --profile <x> starts only the needed services; total RAM of a typical profile < 6 GB in the reference project.
  • A remote service appears in status/logs like a local one.

Related: #124, #125.

Lenguaje dominante
Rust
Estrellas
3
Forks
1
Merge medio
9 h 51 min
PR fusionados (30 d)
310

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de codeatlasdev/atlas

Todos los issues de codeatlasdev/atlas

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.