Andy DixonandClaude
53968f8822
README, CLAUDE.md, man pages, the user guide and its screenshot script now describe the Rust build and the intentional behaviour changes, which docs/MIGRATION.md lists. Go and Rust micro-benchmarks for the same operations, and scripts/bench.sh for end-to-end comparison. build.sh exports its tree root to the per-target jobs and keeps logs out of the output directory; riscv64 musl builds use getrandom's raw syscall backend, since zig's musl getrandom never reaches the kernel there. Co-Authored-By: Claude <noreply@anthropic.com>
45 lines
1.2 KiB
Groff
45 lines
1.2 KiB
Groff
.TH VAULT-MIGRATE 1 "October 2026" "vault" "User Commands"
|
|
.SH NAME
|
|
vault-migrate \- move files into the vault, deleting the originals
|
|
.SH SYNOPSIS
|
|
.B vault migrate
|
|
.RB [ \-\-yes ]
|
|
.RB [ \-\-key
|
|
.IR PATH ]
|
|
.RB [ \-\-vault
|
|
.IR DIR ]
|
|
.IR FILE | DIR
|
|
.RI [ FOLDER ]
|
|
.SH DESCRIPTION
|
|
Works like
|
|
.BR vault\-add (1)
|
|
but deletes each original once it is stored (and its record is on disk),
|
|
then any directories left empty. An original is deleted only if it is still
|
|
the same file, unchanged, that was stored; otherwise it is kept and the
|
|
command fails.
|
|
Directories still holding skipped files stay. A URL cannot be migrated.
|
|
.PP
|
|
Before storing anything it lists the vault names that would be overwritten and
|
|
asks for confirmation on the terminal. With no terminal the answer is no, and
|
|
nothing changes.
|
|
.SH OPTIONS
|
|
.TP
|
|
.B \-\-yes
|
|
Overwrite without asking.
|
|
.SH OPTIONS
|
|
.TP
|
|
.BI \-\-key " PATH"
|
|
Key file. Default: $VAULT_KEY, else ~/.vault/key.
|
|
.TP
|
|
.BI \-\-vault " DIR"
|
|
Vault directory. Default: $VAULT_DIR, else ~/.vault/store.
|
|
.SH ENVIRONMENT
|
|
.TP
|
|
.B VAULT_PASSPHRASE
|
|
Passphrase, instead of prompting on the terminal.
|
|
.SH SEE ALSO
|
|
.BR vault (1),
|
|
.BR vault\-add (1)
|
|
.SH AUTHOR
|
|
Andy Dixon <vault@dixon.cx>, https://www.dixon.cx
|