Passlock Distributed Directory
The current directory for passlock is very simple, where the binary reads from a single passlock.vault file in root. This has to be changed for enhanced safety and organisation. For that reason, a better directory structure for the binary to act on is to be implemented.
1. What this directory would look like:
.passlock
├── backups
│ └── <vault_name>
│ ├── backup_20XX-XX-XX_XX-XX-XX.vault
│ └── backup_20XX-XX-XX_XX-XX-XX.vault
│ └── backup_20XX-XX-XX_XX-XX-XX.vault
├── config.json
└── vaults
└── <vault_name1>.vault
└── <vault_name2>.vault
- The .passlock/ would be present in the root directory.
- backups/ contain upto 10 backups (default), which are either auto-generated or manually created.
- The Backups subdirectory is broken down into backups for different vaults under their respective names.
- config.json contains basic user preference data, user can edit this or use the TUI to edit.
- vaults/ contains the different vaults which the CLI and TUI read from.
- The Vaults subdirectory is not further broken down to prevent complications.
2. This new structure enables multiple vault creation.
3. It allows user preferences to be saved and used.
4. It allows backups to be saved for zero-data-loss.
5. It ensures that backups are always put into their respective vault's subdirectories to prevent corruption.
With this, I end this issue. Any updates regarding this topic will be notified in this issue itself.
Passlock Distributed Directory
The current directory for passlock is very simple, where the binary reads from a single passlock.vault file in root. This has to be changed for enhanced safety and organisation. For that reason, a better directory structure for the binary to act on is to be implemented.
1. What this directory would look like:
2. This new structure enables multiple vault creation.
3. It allows user preferences to be saved and used.
4. It allows backups to be saved for zero-data-loss.
5. It ensures that backups are always put into their respective vault's subdirectories to prevent corruption.
With this, I end this issue. Any updates regarding this topic will be notified in this issue itself.