How yurikrupnik/mussia33 works
Project type and purpose
• This is a polyglot, monorepo‐style full-stack workspace managed by Nx.
• It contains multiple “apps” (SolidJS frontend, REST/gRPC back-ends in Deno, Go, Node, Rust), shared “libs,” and infrastructure definitions (Pulumi/IaC, Kubernetes manifests, Crossplane/CUE packages).
• CI/CD is driven by CircleCI and GitHub Actions; Tilt and Taskfile.yaml scripts orchestrate local dev environments.
File structure
• Top-level folders:
– apps/: each subfolder is a deployable microservice or front-end (apps/deno, apps/frontend, apps/go, apps/node, apps/rust, apps/iac).
– libs/: shared code and gRPC/Proto bindings used by multiple services.
– platform/ & k8s/: cluster definition, GitOps (ArgoCD/Flux), Crossplane compositions, CUE modules.
– .github/ & .circleci/: CI pipelines for build, lint, test, Docker image lifecycle.
– clusters/: Flux-managed cluster bootstrap config.
– Tiltfile, Taskfile.yaml: developer environment orchestration.
• Configuration: Dockerfiles (multiple runtimes), Tiltfiles, Pulumi configs (apps/iac), Crossplane YAMLs, Kubernetes Kustomize overlays.
README
• Confirms it is an Nx workspace for large “mono-repo” with dependency graphing (nx graph).
• Encourages remote caching and explains that Nx is the orchestrator.
Key reminders
– Be exhaustive: include every app, every lib, and each infra component.
– Show data flows clearly (which service calls which).
– Capture all essential architectural elements; monorepo, polyglot microservices, IaC, GitOps, and developer tooling.