Factory reset

Both resets are destructive and require typing the exact phrase purge everything, then force everything to be paired again.

Storage NodeCopy Anchor Link

From the interactive CLI choose Factory reset (delete everything), or from the running shell:

nodus> factory-reset

This deletes the node's catalogue, objects, identity, and config. The node gets a new node_id, so it must be paired with the Relay again.

RelayCopy Anchor Link

Stop the running Relay first, then:

cd services/relay
go run . --factory-reset            # prompts: type "purge everything"
# or non-interactively:
echo 'purge everything' | go run . --factory-reset

This drops and recreates the database schema (rebuilt from migrations on the next start), flushes the Relay's Redis database, and clears the shard buffer. Every account, device, and Storage Node must register and pair again.

The prompt prints the exact targets it is about to destroy — Postgres host and database, Redis host and index, and the buffer path — with credentials removed, so a DATABASE_URL or REDIS_URL aimed at the wrong place is visible before anything is deleted.

GuardrailsCopy Anchor Link

• The reset refuses to run while another client is still connected to the database, because dropping the schema under a live server leaves it erroring against missing tables. If the only remaining connection is yours (a psql session, say), pass --factory-reset-force.
• BUFFER_DIR is validated before anything is deleted. A relative path, the filesystem root, a system directory (/etc, /usr, /tmp, …), your home directory, the working directory, or a path that resolves through a symlink into a system tree is refused outright — os.RemoveAll is recursive, so those values would delete far more than the shard buffer. Use a dedicated subdirectory such as /var/lib/nodus/buffer.

RelatedCopy Anchor Link

• Configuration
• Storage Node operations