how_datvault_works
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
how_datvault_works [2021/11/19 20:10] โ created johnsanc | how_datvault_works [2021/11/28 06:52] โ [DATVault JSON Files] johnsanc | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== How does DATVault | + | ====== How DATVault |
+ | DATVault acts as an indexing, updating, and delivery service for DATs. DATVault is designed to be flexible and it does not force you to organize your DATs in any specific way. | ||
+ | {{ : | ||
+ | |||
+ | ===== 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 repository to determine if there are updates available to download. | ||
+ | |||
+ | The DATVault JSON files contain the following keys: | ||
+ | * **'' | ||
+ | * **'' | ||
+ | * **'' | ||
+ | * **'' | ||
+ | * **'' | ||
+ | * **'' | ||
+ | * **'' | ||
+ | * **'' | ||
+ | * **'' | ||
+ | |||
+ | **Example DATVault JSON for MAME:** | ||
+ | < | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | |**๐ 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