nazim/avault
1
0
Fork 1
Code Issues 7 Pull requests 3 Projects Releases Packages Wiki Activity Actions

feat: install script + data dir at ~/.avault/ #14

Open
nazim wants to merge 1 commit from feat/install-script into main
pull from: feat/install-script
merge into: nazim:main
Conversation 0 Commits 1 Files changed 2 +148 -7
nazim commented 2026-02-27 14:46:33 +00:00
Owner
Copy link

Changes

install.sh

  • Clones repo to ~/.avault/avault/
  • Checks Python 3.11+ and nostr-sdk dependency
  • Symlinks avault to ~/.local/bin/ (default) or /usr/local/bin/ (--system)
  • Handles fresh install and updates (git pull)
  • Prints next steps

avault.py — data directory change

  • AVAULT_HOME defaults to ~/.avault/ (was ~/clawd/)
  • Falls back to WORKSPACE env for backward compatibility
  • Vault data files (avault.enc, nsec.enc, nip46.json) live in ~/.avault/ — parent of the repo clone, not inside it

Layout after install

~/.avault/
  avault.enc       # vault data (user data, not in repo)
  nsec.enc         # encrypted nsec
  nip46.json       # NIP-46 config
  avault/          # git repo clone
    scripts/avault.py
    install.sh
    SKILL.md
    ...

Tested

  • Fresh install via bash install.sh --system
  • Existing vault data migrated to ~/.avault/
  • avault list / avault get work with new paths
  • vault_helper.py (agent script integration) still works

Closes #10

## Changes ### install.sh - Clones repo to `~/.avault/avault/` - Checks Python 3.11+ and nostr-sdk dependency - Symlinks `avault` to `~/.local/bin/` (default) or `/usr/local/bin/` (`--system`) - Handles fresh install and updates (`git pull`) - Prints next steps ### avault.py — data directory change - `AVAULT_HOME` defaults to `~/.avault/` (was `~/clawd/`) - Falls back to `WORKSPACE` env for backward compatibility - Vault data files (`avault.enc`, `nsec.enc`, `nip46.json`) live in `~/.avault/` — parent of the repo clone, not inside it ### Layout after install ``` ~/.avault/ avault.enc # vault data (user data, not in repo) nsec.enc # encrypted nsec nip46.json # NIP-46 config avault/ # git repo clone scripts/avault.py install.sh SKILL.md ... ``` ### Tested - Fresh install via `bash install.sh --system` - Existing vault data migrated to `~/.avault/` - `avault list` / `avault get` work with new paths - `vault_helper.py` (agent script integration) still works Closes #10
feat: install script + data dir at ~/.avault/
Some checks failed
Tests / test (pull_request) Failing after 4s
Details
26a1547ae1 
- Add install.sh: clones repo to ~/.avault/avault/, checks deps,
  symlinks avault to PATH
- Change data directory from WORKSPACE to AVAULT_HOME (~/.avault/)
- Falls back to WORKSPACE env for backward compatibility
- Vault data (avault.enc, nsec.enc, nip46.json) lives in ~/.avault/
  (parent of repo), not inside the repo

Closes #10
Some checks failed
Tests / test (pull_request) Failing after 4s
Details
This pull request has changes conflicting with the target branch.
  • scripts/avault.py
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feat/install-script:feat/install-script
git switch feat/install-script

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff feat/install-script
git switch feat/install-script
git rebase main
git switch main
git merge --ff-only feat/install-script
git switch feat/install-script
git rebase main
git switch main
git merge --no-ff feat/install-script
git switch main
git merge --squash feat/install-script
git switch main
git merge --ff-only feat/install-script
git switch main
git merge feat/install-script
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nazim/avault!14
No description provided.