Hatch.surf web application
027e9a4a49
TestSmokeE2E starts a real server and exercises the full product flow: - Phase 1: Health check (liveness probe) - Phase 2: Capture all 5 HTTP methods, verify stored - Phase 3: Inspect page renders HTML with request cards, replay UI, SSE script - Phase 4: SSE stream receives live events on capture - Phase 5: Mock configuration and response (set mock → capture returns mock) - Phase 6: Replay a captured request to a sink server - Phase 7: Edge cases (query params, binary body, SSRF protection) The one-command gate: go test ./cmd/hatch -run TestSmokeE2E -v Also fix .gitignore: the bare 'hatch' entry was matching cmd/hatch/ directory, preventing test files from being tracked. Narrowed to /hatch (root binary only) and hatch.exe. Co-Authored-By: Paperclip <noreply@paperclip.ing> |
||
|---|---|---|
| .github/workflows | ||
| brand | ||
| cmd/hatch | ||
| docs | ||
| internal | ||
| .dockerignore | ||
| .env.example | ||
| .gitignore | ||
| Caddyfile | ||
| CONTRIBUTING.md | ||
| docker-compose.yml | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| README.md | ||
El Foundation
Engineering repository for El Foundation.
About
El Foundation builds institutions that outlast their founders. We create technology and organizations that compound in value over time. This repository is the source of truth for our engineering work.
Getting Started
- Read the company charter to understand why we exist.
- Read the operating model to understand how decisions are made.
- Read CONTRIBUTING.md before making any changes.
Repository Layout
├── .github/workflows/ # CI/CD definitions
├── docs/
│ ├── company/ # Founding documents (charter, org, etc.)
│ ├── engineering/ # Engineering standards and decisions
│ └── adrs/ # Architecture Decision Records
├── apps/ # Application code (TBD — created when product work begins)
├── packages/ # Shared libraries and packages
└── scripts/ # Automation and utility scripts
Hatch — Deploy in one command
Hatch is a self-hostable HTTP request inspector + mocker. Ship it to any VPS with Docker.
Quick start (local dev, no HTTPS)
docker compose up --build
# Hatch UI: http://localhost:8080
# Capture endpoint: http://localhost:8080/{endpoint-id}
Production (with HTTPS via Caddy)
# Set your domain name
cp .env.example .env
# Edit HATCH_HOSTNAME in .env to your real domain
# Start Hatch + Caddy (auto-issues Let's Encrypt cert)
docker compose --profile with-caddy up -d --build
# Hatch UI: https://{your-domain}
# Capture endpoint: https://{your-domain}/{endpoint-id}
Architecture
Internet → :443 (Caddy) → hatch:8080 (Go binary, internal network)
│
├─ Auto TLS (Let's Encrypt, or self-signed for localhost)
├─ Reverse proxy with security headers
└─ JSON access logs to stdout
Caddy terminates TLS and reverse-proxies to the Hatch Go binary. The Hatch container only listens on 127.0.0.1:8080 — it's never directly exposed to the internet.
Technology Stack
See docs/engineering/tech-stack.md for current choices and rationale.
Contributing
See CONTRIBUTING.md.
License
Proprietary — All rights reserved.