Skip to main content

​
GitHub Organization Setup Summary

Organization: nestr-tools Setup Date: 2026-02-14 Total Repositories: 11

​
Overview

This document provides a comprehensive overview of the GitHub organization structure created based on architectural specifications found in this repository.

​
Repository Inventory

RepositoryCategoryVisibilityTemplateDescription
.githubOrganizationalPrivateNoOrganization profile and configs
engineBackend ServicePrivateNoGo backend: REST API, CLI, Pellets
webFrontend AppPrivateNoVite/React dashboard
perchInfrastructurePrivateNoK8s observability stack
service-templateTemplatePrivateYesGo microservice template
frontend-templateTemplatePrivateYesVite/React app template
platform-docsDocumentationPrivateNoArchitecture docs, runbooks
terraform-infrastructureInfrastructurePrivateNoTerraform IaC modules
helm-chartsInfrastructurePrivateNoK8s Helm charts
sweepUtilityPrivateNoCross-language directory scanner
ci-cd-pipelinesInfrastructurePrivateNoShared GitHub Actions workflows

​
Repository Breakdown by Category

CategoryCountRepositories
Backend Services1engine
Frontend Applications1web
Infrastructure4perch, terraform-infrastructure, helm-charts, ci-cd-pipelines
Templates2service-template, frontend-template
Documentation1platform-docs
Utilities1sweep
Organizational1.github

​
Architecture Principles Applied

​
1. Horizontal Scalability First

  • Each service designed to scale independently
  • Stateless services with external state stores
  • Load balancer-ready architecture

​
2. Bounded Contexts (DDD)

  • Clear domain boundaries
  • Each service owns its data model
  • Well-defined interfaces

​
3. Deployment Independence

  • Services can deploy without coordination
  • Independent release cycles
  • Backward-compatible API changes

​
4. Team Autonomy

  • Repository boundaries align with team boundaries
  • Full lifecycle ownership per team
  • Minimal cross-team coordination needed

​
Dependency Graph

​
Technology Landscape

TechnologyRepositories
Goengine, service-template, sweep
TypeScript/Reactweb, frontend-template
Terraformterraform-infrastructure
Helm/Kuberneteshelm-charts, perch
GitHub Actionsci-cd-pipelines
Prometheus/Grafanaperch
RepositoryURL
enginehttps://github.com/nestr-tools/engine
webhttps://github.com/nestr-tools/web
perchhttps://github.com/nestr-tools/perch
service-templatehttps://github.com/nestr-tools/service-template
frontend-templatehttps://github.com/nestr-tools/frontend-template
platform-docshttps://github.com/nestr-tools/platform-docs
terraform-infrastructurehttps://github.com/nestr-tools/terraform-infrastructure
helm-chartshttps://github.com/nestr-tools/helm-charts
sweephttps://github.com/nestr-tools/sweep
ci-cd-pipelineshttps://github.com/nestr-tools/ci-cd-pipelines

​
Next Steps

PriorityTaskEstimated Effort
CriticalConfigure branch protection on all repos30 min
HighSet up CI/CD pipelines in each repo2-3 hours
HighCreate CODEOWNERS files for existing repos30 min
MediumDocument inter-service APIs1-2 hours
MediumSet up issue/PR templates30 min
LowConfigure Dependabot for dependency updates30 min

​
Using Template Repositories

​
Create New Go Service

gh repo create nestr-tools/my-new-service \
  --template nestr-tools/service-template \
  --private

​
Create New Frontend App

gh repo create nestr-tools/my-new-app \
  --template nestr-tools/frontend-template \
  --private

​
Using Shared CI/CD Workflows

Reference workflows from ci-cd-pipelines in your repository: 
# .github/workflows/ci.yml
name: CI

on:
  push:
    branches: [main]

jobs:
  build:
    uses: nestr-tools/ci-cd-pipelines/.github/workflows/go-ci.yml@main
    with:
      go-version: '1.24'
    secrets: inherit
Document Generated: 2026-02-14 Generator: Architecture-Driven GitHub Organization Setup