how_datvault_works
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
how_datvault_works [2021/11/19 20:45] – johnsanc | how_datvault_works [2021/11/28 06:55] – johnsanc | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== How DATVault Works ====== | ====== How DATVault Works ====== | ||
- | DATVault | + | DATVault |
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== DATVault JSON Files ===== | ||
+ | |||
+ | DATVault works by detecting special JSON files in your DatRoot. Each DAT you would like to manage has its own corresponding JSON file. Each file provides info about the DAT version you currently have. This info is compared against the DATVault | ||
The DATVault JSON files contain the following keys: | The DATVault JSON files contain the following keys: | ||
Line 27: | Line 33: | ||
} | } | ||
</ | </ | ||
+ | |||
+ | If the JSON file you have does not match the latest version available by DATVault, then the corresponding DAT has an update. When you update a DAT, the JSON file is also updated. | ||
+ | |||
+ | |**🛈 NOTE:** \\ DATVault will download any updates into the same directory that contains the respective JSON file. Any existing DATs for that system will have a '' | ||
+ | |||
+ | Now that you understand how DATVault works at a high level, refer to the next section to [[datvault_setup|get started using DATVault]]. |
how_datvault_works.txt · Last modified: 2023/07/04 08:38 by johnsanc