mirror of
https://github.com/PR0M3TH3AN/SeedPass.git
synced 2026-10-27 07:52:03 +00:00
Load relays from config
This commit is contained in:
1 parent
1163f5eac4
commit
d124b42a1f
3 files changed
+401
-194
No files matched your search
@@ -237,8 +237,9 @@ The SeedPass roadmap outlines a structured development plan divided into distinc
|
||||
- **Implementation Steps:**
|
||||
- Create a `config.yaml` or `config.json` file in the SeedPass data directory.
|
||||
- Define a structure to store user configurations, starting with a list of Nostr relay URLs.
|
||||
- Allow users to add, remove, and manage an unlimited number of Nostr relays through the CLI or configuration file.
|
||||
- Ensure the configuration file is securely stored and encrypted if necessary.
|
||||
- Allow users to add, remove, and manage an unlimited number of Nostr relays through the CLI or configuration file.
|
||||
- Ensure the configuration file is securely stored and encrypted if necessary.
|
||||
- The Nostr client loads its relay list from this encrypted file. New accounts start with the default relays until you update the settings.
|
||||
|
||||
2. **Individual JSON File Management**
|
||||
- **Separate Entry Files:**
|
||||
|
||||
@@ -418,6 +418,7 @@ seedpass show-pubkey
|
||||
|
||||
**Description:**
|
||||
Allows users to specify custom Nostr relays for publishing their encrypted backup index, providing flexibility and control over data distribution.
|
||||
Relay URLs are stored in an encrypted configuration file and loaded each time the Nostr client starts. New accounts use the default relays until changed.
|
||||
|
||||
**Usage Example:**
|
||||
```bash
|
||||
|
||||
+397
-192
File diff suppressed because it is too large.
Load diff
Reference in new issue
Block a user