Kyle Isom 37c2d35ceb Implement Phase 6: REST API with chi router
- Login endpoint (password → bearer token + session cookie)
- Auth middleware (bearer header or session cookie)
- Notebook list endpoint (authenticated)
- Page SVG/JPG rendering endpoints (authenticated)
- Notebook PDF download endpoint (authenticated)
- Share link endpoints: view, page SVG, page JPG, PDF (no auth)
- Route registration with chi groups

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-24 19:55:47 -07:00

eng-pad-server

Read-only sync and web viewer for eng-pad engineering notebooks.

The Android app pushes complete notebooks to this server via gRPC. The server stores them and serves read-only views through a web UI with SVG rendering. Shareable links allow unauthenticated access to specific notebooks.

Features

  • gRPC sync: receive notebook data from the Android app over TLS
  • Web viewer: browse notebooks, view pages as SVG, export JPG/PDF
  • Authentication: password (Argon2id) + FIDO2/U2F security keys
  • Shareable links: token-based URLs with optional expiry

Quick Start

# Build
make eng-pad-server

# Generate example config
cp eng-pad-server.toml.example /srv/eng-pad-server/eng-pad-server.toml
# Edit configuration (TLS certs, database path, etc.)

# Initialize (creates database, prompts for admin user)
./eng-pad-server init

# Run
./eng-pad-server server

Build

make all          # vet → lint → test → build
make test         # run tests
make lint         # golangci-lint
make proto        # regenerate gRPC code from .proto files
make proto-lint   # buf lint + breaking change detection

Documentation

License

Private. All rights reserved.

Description
No description provided
Readme 375 KiB
Languages
Go 87.1%
HTML 11%
Shell 0.9%
Makefile 0.6%
Dockerfile 0.4%