Inspectora quickstart: install in minutes

INSPECTORA — QUICKSTART
=======================

Self-hosted inspection, calibration and logbook tracker — PHP + MySQL/SQLite.
Records that a check happened, whether it passed, and when the next one is
due. It is NOT a work-order system and it does NOT issue certificates (see
"WHAT IT IS NOT").


REQUIREMENTS
------------
  - PHP 8.0+ with extensions: pdo, pdo_sqlite (or pdo_mysql)
  - MySQL 5.7+ / MariaDB 10+ OR SQLite 3 (SQLite requires no extra setup)
  - A web server (Apache with mod_rewrite, or Nginx with try_files)
  - No Composer packages, no API keys, no external services.


SHARED HOSTING / CPANEL (RECOMMENDED FOR MOST BUYERS)
------------------------------------------------------
1. Upload the contents of the `app/` folder to your web root (e.g. public_html/)
   or a subdirectory (e.g. public_html/inspectora/).
2. Make sure `data/` is writable by the web server (chmod 775 usually does it).
3. Open the address in a browser. The installer runs on the first visit.
4. Create your admin login when asked, then sign in.


FIRST TEN MINUTES
-----------------
1. ASSETS — add everything you inspect, test or calibrate, or bring a list in
   from a spreadsheet under Import. Give each one a CLASS (Extinguishers,
   Calibration, Portable, Water systems...) — that is what scopes the checks.
2. INSPECTION TYPES — add the checks, and how many months each is good for.
   Use 0 for something with no recurring due date (a commissioning record).
   Leave "Applies to" blank for every asset, or type a class to scope it.
   Keep classes NARROW: put everything in one "Fire equipment" bucket and the
   board will ask whether an extinguisher passed its fire-alarm test.
3. WHAT IS DUE — the board fills itself. Click any cell to record an
   inspection and its result (pass, pass with remarks, fail); the next-due
   date is computed from the interval, so you never type one. A fail sets no
   next-due date and the cell reads "failed" until a later pass. Filter to
   Failed, Expired or Never recorded for the day's work list.
4. SCHEDULES (optional) — plan a round, put the assets on it, tick what was
   actually done and pick each one's result. Each one gets a record written
   for it.


DUE REMINDERS (OPTIONAL, OFF BY DEFAULT)
----------------------------------------
Settings -> Email. Put in YOUR OWN SMTP server. Nothing is routed through
anyone else. Then point a daily schedule at:

    php /path/to/app/cron/reminders.php

Use --dry-run first: it lists who would be written to and sends nothing.
Inspectora runs no background job of its own. If nothing runs that file,
nothing is sent. No cron on your host? Settings -> "Run reminders now"
runs the same pass, and Settings shows when it last ran.


BACKUPS
-------
Settings -> Data & access -> Backup (JSON), or the whole SQLite file. The
restore screen shows a dry-run diff before it writes anything.


WHAT IT IS NOT
--------------
  - It does NOT issue certificates. Attach the one your inspector or lab gives
    you to the record it evidences.
  - It is NOT a CMMS or work-order system: no jobs, engineers, parts or costs.
  - It does not read meters, sensors or barcodes — a person enters everything.
  - Assets are records, not users: no portal, no QR code on the extinguisher.
  - An inspection type applies to every asset or to ONE class tag. There is no
    rule language, so a mixed register gives a deliberately sparse board.
  - Changing an interval does not rewrite records already on file.
  - Single organisation per installation.


TROUBLESHOOTING
---------------
  - "Database connection failed" — check data/ is writable, or your MySQL
    credentials in config.php.
  - A blank page — turn on PHP error display, or check the server error log.
  - Cells you expected are hatched ("does not apply") — the inspection type is
    scoped to a class that does not match that asset's.