# Seeding node

A seeding node indexes old article ranges for the indexer (CONCEPT.md D37,
D38). It asks the seed API for a range over HTTPS, fetches that range's
headers over its own NNTP connections, groups them into files, and posts the
result back. It only makes outgoing connections: no port forwarding, database
or Redis.

On the indexer (homelab):

    docker compose exec web node ace seed:token my-server         # prints the node's token once
    docker compose exec web node ace seed:plan alt.binaries.ath --days 365
    docker compose exec web node ace seed:status

On the node (any machine with Docker):

    cp node.env.example node.env     # SEED_TOKEN, NNTP account, SEED_CONNECTIONS
    docker compose up -d --build
    docker compose logs -f

`docker compose stop` gives the node's ranges back; a node that disappears
loses its ranges to other nodes after 15 minutes without a batch. Updating:
`docker compose up -d --build` again.

Mind the NNTP account's connection limit: every node's SEED_CONNECTIONS
count against it, next to the indexer's own connections.