Where Setup puts everything. The rule is one: when the computer has a fixed drive D that can be written to, the program, its data and its backups go on it. Otherwise the program goes in Program Files and its data and backups in ProgramData, because a program under Program Files never holds its own database.
B.1 The main folders
Folder
With a drive D
Without a drive D
The program
D:\Clarus\Clarus_prime
C:\Program Files\Clarus\Clarus_prime
The data
D:\Clarus\Clarus_prime\data
C:\ProgramData\Clarus\Clarus_prime\data
The backups
D:\Clarus\Clarus_prime-backups
C:\ProgramData\Clarus\Clarus_prime-backups
The kept copy of the licence
C:\ProgramData\Clarus\Clarus_prime-licence
C:\ProgramData\Clarus\Clarus_prime-licence
An installation's actual paths are written in the configuration file clarus-lis.config.json in the program's folder, in the fields install_dir, data_dir, logs_dir and postgres_data_directory. If the technician chose another folder at installation, the file is the reference.
B.2 Inside the program's folder
Path
What it holds
clarus-lis.config.json
The configuration file: the port, the paths, and the database's address and password
runtime\python
The program's own Python environment
runtime\postgresql\pgsql\bin
The PostgreSQL programs
packaging\windows
The scripts that start and stop the program and set up the database
clarus_lis\language_packs
The installed language packs
install-transcript.log
The installation log
B.3 Inside the data folder
Path
What it holds
pgdata
The database itself. Nothing in it is touched by hand
cluster-superuser.json
The database's two passwords
security
The encryption keys: field_vault.key for the sensitive fields, and backup.key that signs the backups and checks them