Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

Ai-Simple-Rag-with-Go-Nextjs

Created with Better Fullstack.

Applications and resources

  • next (typescript, frontend): apps/web; part frontend:typescript:next
  • gin (go, backend): apps/server; part backend:go:gin
  • postgres (universal, database): packages/db; part database:universal:postgres
  • turborepo (universal, workspaceRunner): .; part workspacerunner:universal:turborepo

Setup

Install the SDKs for the selected languages before preparing dependencies. SwiftUI needs macOS, Xcode, and XcodeGen; Kotlin Android apps need a JDK and Android SDK; Flutter needs the Flutter SDK. Rust web apps also need the WebAssembly target and Trunk or Dioxus CLI.

JavaScript dependencies are installed at the workspace root. Each native application keeps its own toolchain. Native package scripts require bash on PATH; install Git Bash on Windows. Run the shell commands below in Bash.

If dependencies were not prepared during creation, run:

bun install
(cd apps/server && go mod tidy)

Copy each application's .env.example to .env when present and configure database credentials before starting database-backed services.

Local development

Start the selected web applications and backend services together:

bun run dev

The supervisor stops the other services when one exits. Native mobile applications run separately so you can choose a simulator or device. Open Kotlin applications in Android Studio.

Go Gin

Run independently from the project root:

cd apps/server && go run cmd/server/main.go

Connections

  • Go Gin (default client connection): http://localhost:8080, health endpoint http://localhost:8080/health.

Cross-language clients communicate over HTTP. Framework-specific clients such as tRPC are used only with compatible backends. Generated connection files identify the default backend; additional services retain their own paths and endpoints.

Harness Engineering

Este repositorio trabaja bajo un harness engineering inspirado en ejemplo-harness-subagentes: el repo ES el sistema, una feature a la vez, estado en disco, verificación ejecutable.

Organización del arnés

Pilar Manifestación en este repo
1. El repositorio ES el sistema AGENTS.md, init.sh, feature_list.json, progress/, docs/
2. Orquestación multi-agente .claude/agents/leader.md, implementer.md, reviewer.md
3. Supervisión y mejora CHECKPOINTS.md, hooks en .claude/settings.json

Para empezar

./init.sh

Si todo está verde, abre AGENTS.md y sigue desde ahí.

Receta rápida

  1. ./init.sh — debe terminar verde.
  2. Abre feature_list.json y elige una feature con status: "pending".
  3. Un agente (o tú a mano) implementa esa única feature, escribe sus tests, corre ./init.sh y la pasa a done.

Próximas features (todas pending en feature_list.json): chunking → embeddings → almacenamiento vectorial (pgvector) → API de ingestión → búsqueda semántica → chat RAG → UI web.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages