# Deployment notes — this package

Generated for the `xnzgc0gigsjr3cg6_monthly_ledger` database at
`cqvie.airtechdocs.com`, following `docs/DEPLOY.md`.

## What was changed

`includes/config.php` — the only file that needed edits (by design, Section
10.1 of the blueprint):

| Setting | Old (local XAMPP) | New (this package) |
|---|---|---|
| `DB_HOST` | `localhost` | `mysql` (from your `connection.php`) |
| `DB_NAME` | `monthly_ledger` | `xnzgc0gigsjr3cg6_monthly_ledger` |
| `DB_USER` | `root` | `xnzgc0gigsjr3cg6_root` (from your `connection.php`) |
| `DB_PASS` | *(empty)* | `AIRtech@DOCs#2023` (from your `connection.php`) |
| `APP_ENV` | `development` | **left as `development`, on purpose — see below** |

Your `connection.php` pointed at `xnzgc0gigsjr3cg6_cqvie` — that's your
existing project's database. This app's own database, already created on
your host, is `xnzgc0gigsjr3cg6_monthly_ledger` (confirmed from your
screenshot). I used your host/user/password but corrected the database
name so this app doesn't touch your other project's data.

Everything else (file paths, `fetch()` calls, session cookies, `.htaccess`
rules) already uses relative paths and `__DIR__`, so nothing else needed to
change to move off XAMPP — I checked the whole codebase for hardcoded
`localhost`/absolute-path references and found none outside `config.php`.

## Two things I could not verify or decide for you

**1. Whether the live database already has data in it.**
Your screenshot shows the tables exist, but not whether they're populated.
I can't connect to `cqvie.airtechdocs.com` from here to check. In
phpMyAdmin, open the `users` table:
- **Has rows already?** You're done — skip straight to logging in.
- **Empty?** Import `database/seed.sql` (schema is already there, so skip
  `schema.sql`). If you'd rather bring over the data from your local
  XAMPP testing (two users already past the temporary-password step, plus
  any test expenses), import `backups/monthly_ledger-full-backup-20260703-164024.sql`
  instead — it's a full self-contained dump (`DROP TABLE` + `CREATE TABLE`
  + data), so it replaces the empty tables outright.

**2. `APP_ENV` is left as `'development'`.**
This shows real PHP errors on screen instead of a generic message — useful
for your first login/DB-connectivity check, since I can't smoke-test this
deployment myself. Once you confirm login and expense entry work:
1. Flip `APP_ENV` to `'production'` in `includes/config.php`.
2. Uncomment the HTTPS-redirect block in `.htaccess` (search "Go-live") —
   only once your host's SSL certificate is confirmed active.
3. Log in as both users and change the seeded temporary passwords.

These three are exactly `docs/DEPLOY.md` steps 4–6, and they're the reason
this can't be fully "zero manual steps": whether your SSL cert is live and
whether the DB already has data are facts only your host/phpMyAdmin can
confirm, not something I can determine from a file review. Steps 1–3 of
that same doc (upload files, create DB, edit config) are already done for
you in this package.

## Recommended first visit

1. Upload everything to `cqvie.airtechdocs.com`'s Monthly Ledger folder.
2. Check the `users` table per point 1 above; seed or restore if empty.
3. Visit the site, log in, add a test expense.
4. If that works, do the three production-hardening steps above.
5. Delete this notes file (and consider moving
   `backups/monthly_ledger-full-backup-20260703-164024.sql` out of the web
   root's `backups/` folder somewhere safer once you've used it — `.htaccess`
   blocks it from being browsed to, but it's still real financial data at rest).
