Skip to content

client: [snapshot] section of config.ini - #88

Merged
EnzinoBB merged 1 commit into
masterfrom
feat/snapshot-config
Oct 24, 2026
Merged

EnzinoBB merged 1 commit into
masterfrom
feat/snapshot-config

Conversation

@EnzinoBB

Copy link
Copy Markdown
Collaborator

Step 2 of snapshots served by community nodes (plan on docs/snapshot-serving).

  • SnapshotData with the keys and defaults of the design (section 8): serving (serve_port 0 = off, serve_bind, serve_max_connections, serve_rate_kbps, snapshot_blocks) and fetching (fetch, sources, sources_file, probe_known_hosts, github_manifest, min_sources 3, fallback github, fetch_connections, fetch_rate_kbps).
  • Config::parseSnapshotData checks ranges and values. A bad value keeps the default with a warning. Empty github_manifest, sources and sources_file mean no such source.
  • The section is part of the comparison the config observer uses, so a change is seen while the node runs.

No behaviour yet. The package defaults (serving on, port 9511, 2 MB/s) and docs/snapshots.md come with the steps that use them.

Tests: defaults without the section, every key, bad values, empty values, comparison.

🤖 Generated with Claude Code

The keys of snapshots served by community nodes (serve_port, serve_bind,
serve_max_connections, serve_rate_kbps, snapshot_blocks, fetch, sources,
sources_file, probe_known_hosts, github_manifest, min_sources, fallback,
fetch_connections, fetch_rate_kbps), with range checks: a bad value
keeps the default with a warning. Part of the comparison the config
observer uses, so changes are seen while the node runs. No behaviour
yet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@EnzinoBB
EnzinoBB merged commit 0298dbd into master Oct 24, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant