Sergei Vasilev
44 lines
1.9 KiB
Markdown
44 lines
1.9 KiB
Markdown
# IQON production-ready state after DB archive gate
|
|
|
|
Purpose: record final live state after legacy hardening, English-only redirects, contact smoke, and verified DB archive creation.
|
|
|
|
Created: 2026-05-20
|
|
Updated: 2026-05-20
|
|
|
|
## Status
|
|
|
|
`COMPLETED` for the current IQON remediation cycle.
|
|
|
|
## Verified production state
|
|
|
|
| Area | Status | Evidence |
|
|
|---|---|---|
|
|
| Apex old design | VERIFIED | `scripts/iqon-phase1-verify.sh https://iqon.com` passed |
|
|
| WWW new design | VERIFIED | `https://www.iqon.com/` contains `theme-color`, `topbar`, `hero-cloud` |
|
|
| English-only redirects | VERIFIED | Encoded RU services URL returns `301` to `/services-solutions/` |
|
|
| Contact form path | VERIFIED | `?sent=ok` page displays `[Your message has been sent.]` |
|
|
| Contact data | VERIFIED | Contact page contains `office@iqon.com` and `@infobidgebot` |
|
|
| DB archive | VERIFIED | Local archive passes `gzip -t`; SQL header already confirmed `Database: u0012812_iqon` |
|
|
|
|
## Current backup artifact
|
|
|
|
| Location | Path |
|
|
|---|---|
|
|
| Remote server | `/var/www/u0012812/data/backups/iqon-u0012812_iqon-20260520-231601.sql.gz` |
|
|
| Local temporary copy | `/private/tmp/iqon-u0012812_iqon-20260520-231601.sql.gz` |
|
|
|
|
Local archive size: approximately `468K`.
|
|
|
|
## Deferred cleanup
|
|
|
|
Two failed remote dump attempts may have left tiny invalid gzip files on the server:
|
|
|
|
1. `iqon-u0012812_default-20260520-231601.sql.gz`
|
|
2. Earlier failed `iqon-u0012812_iqon-20260520-231601.sql.gz` was overwritten by the valid archive path.
|
|
|
|
Cleanup was not performed in this pass because SSH re-check returned `Permission denied`, and deleting files is destructive. If cleanup is required, first restore SSH access, then remove only the confirmed invalid tiny file after listing exact size/path.
|
|
|
|
## Next recommended operational step
|
|
|
|
Move the local `/private/tmp` archive to a durable encrypted backup location outside git, or download/store it through the chosen backup vault process. Do not commit DB dumps to the repository.
|