DigiVC documentation
Command-line transfer client
The public CLI is intentionally limited to two operations:
The public CLI is intentionally limited to two operations:
download— download repository content into a local workspace;upload— upload local changes as a commit.
Full interactive repository and workspace operations belong in the Desktop Client.
Help
digivc --help
digivc download --help
digivc upload --helpLanguage and output format can be selected:
digivc --language en --format text download --help
digivc --format json upload --helpFull download
digivc download \
digivc://digivc.company.example/ERP/Server \
--to "$HOME/work/erp-server" \
--username mariaThe password is entered through a secure prompt.
Partial download
digivc download \
digivc://digivc.company.example/ERP/Server \
/backend/api /database/sql \
--to "$HOME/work/erp-partial" \
--username mariaUpload
Run from the workspace or pass a path:
digivc upload "$HOME/work/erp-server" \
-m "Add input validation" \
--username mariaPassword file for automation
printf '%s\n' 'YOUR_PASSWORD' > "$HOME/.digivc-password"
chmod 600 "$HOME/.digivc-password"
digivc upload "$HOME/work/erp-server" \
-m "Nightly controlled upload" \
--username automation \
--password-file "$HOME/.digivc-password"The password file must:
- be a regular file, not a symlink;
- be owned by the current OS user;
- not be accessible by group or other users;
- not be empty.
Where possible, use a dedicated automation account with minimum permissions instead of a personal administrator account.
Exit and errors
The CLI displays a correlation ID for server errors. Keep it so an administrator can locate the corresponding audit/log event.
If the account requires a password change, complete it in WEB/Admin first.