Everything the product keeps per user lives under one folder, `%USERPROFILE%\Invantive`. Knowing which file holds what answers most questions about "where is this kept" and makes a machine reproducible without guessing. ## The Folder - `settings*.json`: the databases and their data containers, as described under [[Settings]]. A file per source: the one written by hand, and the one automatic discovery fills. - `invantive-own-v2.keychain` and `invantive-keychain-v2.settings`: the [[Invantive Keychain]], where credentials are held encrypted. - `RSA\`: the key material of this device, with which the settings above are encrypted. A settings file copied to another machine without it cannot be read there, which is the point. - `Layout\`: the grid layouts saved with "Display Layout", one file per shape of answer; see [[Invantive Query Tool/Column Layout|Column Layout]]. [[Invantive Query Tool Multi-Platform/Invantive Query Tool Multi-Platform|Invantive Query Tool Multi-Platform]] keeps its layouts in the same folder as `.json` files; see [[Invantive Query Tool Multi-Platform/Display Layout|Display Layout]]. The two products do not read each other's files. - `Cache\`: what the engine keeps between runs, among it the HTTP disk cache. - `Prd\<product>\`: what one product keeps. For Invantive Query Tool that is `sqlhistory.json` with the statements of [[Invantive Query Tool/History|History]], and under `Inst\Query Tool` the file `product-installation-user.settings.json` with the settings of this installation - the licence, the open documents, the counters shown under [[Invantive Query Tool/Preferences|Preferences]]. - `executionlog.ndjson`: one line per run, which is what a question about "when did this last run" is answered from. ## Moving It The environment variable `INVANTIVE_CONFIGURATION_USER_PROFILE_FOLDER` points the whole of the above at another folder, and each of the folders below it can be moved on its own. A run started with the master folder pointed elsewhere touches nothing of the ordinary profile, which is how a demonstration, a screenshot session or a test of a settings file is done on a workstation somebody works on. The variables are listed under [[Folders]]. ## What Not to Edit by Hand The settings files are written by the product and are read again at the next start; editing one while the product runs loses the change. The keychain and the licence in the installation settings are encrypted with the key material of the device and are not editable at all. What is meant to be edited by hand is the settings file of the databases, and the product reads it again on connecting.