Files
ngit-grasp/docs/how-to
DanConwayDev 053ee62610 chore(release): prepare v3.0.9 security patch
Align Cargo and NixOS package versions and collect the accumulated changes in a dated release entry. Put Security first, followed by Fixed and Added, and place the optional historical event audit guidance under Security.

The vulnerabilities were reported from code review with no exploitation reported to us. Admission protection takes effect on upgrade; an offline historical scan is an optional precaution, and purging follows inspection of its report. Preserve the stopped-service requirement and historical recovery limits in both release notes and the repair guide.

This commit changes release metadata and guidance only; it does not alter runtime behavior or publish the release. Validation: locked offline Cargo metadata, Nix module parsing, cargo fmt and git diff checks passed. Implementation CI is checked separately against dfbed25e.

Assisted-by: GPT-6
2026-10-27 10:27:42 +00:00
..
2025-11-04 10:25:53 +00:00

How-To Guides

Task-oriented documentation - Practical solutions to common problems.


What Are How-To Guides?

How-to guides are recipes that show you how to solve specific problems or accomplish particular tasks.

Characteristics:

  • ✅ Task-oriented (solve a problem)
  • ✅ Practical (actionable steps)
  • ✅ Assume basic knowledge
  • ✅ Focus on results
  • ✅ Can be followed in any order

Not how-to guides:

  • ❌ Complete lessons for beginners (those are Tutorials)
  • ❌ Technical specifications (those are Reference)
  • ❌ Conceptual discussions (those are Explanation)

Available How-To Guides

Deploy ngit-grasp

Problem: Run a durable production relay in a supported hosting environment

You'll learn:

  • Choose Docker, NixOS, systemd Linux, Proxmox, or managed hosting
  • Preserve the relay identity, Git repositories, and LMDB state
  • Configure TLS, verify protocols, back up, and upgrade safely

Upgrade from v2 to v3 Git family storage

Problem: Perform the one-way identifier-family storage migration safely Difficulty: Advanced

You'll learn:

  • Prepare capacity and a snapshot-based rollback point
  • Run the automatic crash-safe v3 launch migration
  • Interpret migration and integrity summary logs
  • Restore v2 safely when a release rollback is required

Configure Nix Flakes

Problem: Set up reproducible development environment
Difficulty: Intermediate

You'll learn:

  • Enable Nix flakes
  • Enter development environment
  • Work with subprojects
  • Troubleshoot common issues

Test Sync Against Production Data

Problem: Debug and improve sync using real-world data
Difficulty: Intermediate

You'll learn:

  • Run sync against production relays
  • Sanitize logs for LLM analysis
  • Identify common issues and patterns
  • Iteratively improve sync behavior

Planned How-To Guides

Run Compliance Tests

Status: 🔜 Planned

Problem: Test GRASP compliance
You'll learn:

  • Set up test relay
  • Run integration tests
  • Interpret results
  • Add custom tests

Upgrade nostr-sdk

Status: 🔜 Planned

Problem: Handle breaking changes in nostr-sdk
You'll learn:

  • Check for breaking changes
  • Update dependencies
  • Fix compilation errors
  • Test after upgrade

Configure Authentication

Status: 🔜 Planned (feature not yet implemented)

Problem: Secure your relay
You'll learn:

  • Enable authentication
  • Configure allowed users
  • Set up rate limiting
  • Monitor access

Backup and Restore

Status: 🔜 Planned

Problem: Protect your data
You'll learn:

  • Backup Git repositories
  • Backup Nostr events
  • Restore from backup
  • Automate backups

How to Use How-To Guides

  1. Find your problem - Browse or search for what you need
  2. Check prerequisites - Make sure you have required knowledge
  3. Follow the steps - Adapt to your specific situation
  4. Solve and move on - No need to read everything

Not sure if this is what you need?


Contributing How-To Guides

When writing a how-to guide:

DO:

  • ✅ Start with the problem/goal
  • ✅ List prerequisites clearly
  • ✅ Provide concrete steps
  • ✅ Include troubleshooting
  • ✅ Show examples
  • ✅ Link to related docs

DON'T:

  • ❌ Teach basics (link to Tutorials)
  • ❌ Explain every concept (link to Explanation)
  • ❌ List all options (link to Reference)
  • ❌ Make it a tutorial (stay focused on the task)

Template:

# How-To: [Task/Problem]

**Problem:** [What you're trying to accomplish]  
**Difficulty:** [Beginner/Intermediate/Advanced]  
**Time:** [Estimated time]

## Prerequisites
- [Required knowledge/tools]

## Solution

### Step 1: [Action]
[Instructions]

### Step 2: [Action]
[Instructions]

## Troubleshooting

### [Common problem]
**Solution:** [How to fix]

## Related Documentation
- [Links to relevant docs]

See Diátaxis: How-To Guides for detailed guidance.


Part of the ngit-grasp documentation using the Diátaxis framework.