upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
path: root/docs
AgeCommit message (Collapse)Author
2025-11-21feat: add database backend configuration optionsDanConwayDev
Add environment variable configuration for database backend selection: - Added DatabaseBackend enum (memory, nostrdb, lmdb) in src/config.rs - Updated relay builder to use configured backend in src/nostr/builder.rs - Added NGIT_DATABASE_BACKEND to .env.example with documentation - Updated docs/reference/configuration.md with backend comparison table NostrDB and LMDB backends prepared for future implementation when nostr-relay-builder adds support. Currently defaults to in-memory database with warning logs when persistent backends are selected.
2025-11-18docs: switch focus onto grasp implementationDanConwayDev
2025-11-05preparing to build grasp-audit against git-relayDanConwayDev
2025-11-04docs: archive test migration session notesDanConwayDev
Archive valuable session documentation from test migration project: - Phase 1: NIP-01 compliance test migration - Phase 2: NIP-34 announcement test migration - Phase 3: Test compliance documentation - Final summary: Complete project overview Session cleanup complete - work/ directory now clean (only README.md)
2025-11-04test: migrate to TestRelay fixture pattern and add compliance docsDanConwayDev
- Remove unnecessary 'nix' dev dependency (Unix syscalls crate, not needed) - Migrate announcement tests to new TestRelay fixture pattern - Delete legacy test files (announcement_tests.rs, test_relay.sh) - Add comprehensive test documentation (docs/how-to/test-compliance.md) - Update README.md with new test commands - All 18 integration tests passing (NIP-01 + NIP-34) Benefits: - Automatic relay lifecycle management - No manual setup required - Pure Rust integration tests - Better developer experience - CI/CD ready
2025-11-04docs: use Diátaxis structureDanConwayDev
2025-11-04docs: clean up .txt files and add file format guidelinesDanConwayDev
- Archive 5 .txt files to docs/archive/ - AUDIT_FIX_SUMMARY.txt - PROJECT_STATUS_VISUAL.txt - SESSION_SUMMARY.txt - TEST_VISUAL_SUMMARY.txt - CLEANUP_VISUAL_SUMMARY.txt - Update AGENTS.md with file format guidelines: - When to use .txt (ASCII art only) - When to use .md (all documentation) - .txt lifecycle: create → use → archive immediately - Added to cleanup triggers and checklists Root directory now completely clean: - 4 .md files (README, AGENTS, CURRENT_STATUS, CLEANUP_COMPLETE) - 0 .txt files (all archived) Archive contains: - 33 .md files (historical documentation) - 5 .txt files (visual summaries)
2025-11-04docs: archive cleanup summaryDanConwayDev
2025-11-04docs: major cleanup and reorganizationDanConwayDev
- Archive 30 completed session documents to docs/archive/ - Extract learnings to docs/learnings/ (nix-flakes, nostr-sdk, grasp-audit) - Create CURRENT_STATUS.md as single source of truth - Create AGENTS.md with documentation guidelines - Create docs/archive/README.md for archive organization - Clean root directory: 32 files → 4 files Root directory now contains only: - README.md (project overview) - AGENTS.md (documentation guidelines) - CURRENT_STATUS.md (current state) - CLEANUP_SUMMARY.md (cleanup report) All historical documents preserved in docs/archive/ with proper dating. All reusable knowledge extracted to docs/learnings/. Benefits: - Easy to find current information - Clear document lifecycle - No more documentation sprawl - Learnings are accessible and reusable - Better onboarding for new developers/agents File counts: - Root: 4 (was 32) - Permanent docs: 7 - Learnings: 3 (new) - Archive: 32 (new) - Total: 49 well-organized docs
2025-11-03docs: one-prompt architecture planDanConwayDev
ok 2 prompts, the second one was about the test strategy so we could reuse it. I was thinking of a tool like blossom audit. but i didnt mention it specifically.