Runtime Paths and Overrides

Understand where AutoDoctor stores DB, logs, reports, telemetry, and metadata in development and installed modes, and how environment overrides change behavior.
Categories:
Tags:

Who This Is For

  • Technical users validating storage layout and retention.
  • Developers switching between source and installed workflows.

Default Runtime Roots

Development or Source Execution

If agent exists relative to script root, AutoDoctor treats cloned repo root as home.

Example:

D:\src\AutoDoctor\

Installed Execution

Default install/runtime root:

C:\ProgramData\AutoDoctor\

Path Mapping

Logical path Resolved directory
Root <AUTO_DOCTOR_HOME or inferred root>
DB root\db
Reports root\reports
Telemetry root\telemetry
Diagnostics root\diagnostics
Logs root\logs
Config root\config
Dashboard/meta folder root\server

File Mapping

File Default location
SQLite DB db\autodoctor.db
HTML report reports\AutoDoctor_Report.html
JSON report reports\AutoDoctor_Report.json
Agent log logs\autodoctor.log
API/service log logs\autodoctor_api.log
Dashboard metadata server\latest_run.json

Environment Overrides 

$env:AUTO_DOCTOR_HOME = "D:\Ops\AutoDoctor"
$env:AUTO_DOCTOR_DB_PATH = "D:\Ops\AutoDoctor\db\autodoctor_custom.db"
$env:AUTO_DOCTOR_CONFIG_INI = "D:\Ops\AutoDoctor\config\autodoctor.ini"
$env:AUTO_DOCTOR_API_HOST = "127.0.0.1"
$env:AUTO_DOCTOR_API_PORT = "8000"

Effects:

  • AUTO_DOCTOR_HOME relocates most runtime folders.
  • AUTO_DOCTOR_DB_PATH overrides only DB file path.
  • API host/port vars affect service bind only if registry/INI does not override.

Next Steps