Security and going live
What protects the marketplace, the Health & Security Check page and its groups, going live step by step, backups / updates / rollback, and what the product does for performance.
2.0.0 is the production release: the code was audited, the web-server rules hardened, and the admin area got a checklist that tests the real server. This chapter is the owner's view of it; the developer notes are in the product's docs/06-security.md and docs/07-operations.md.
1. What protects the marketplace
- Accounts: hashed passwords with a policy, sign-in throttling (five failures hold the address off for fifteen minutes), two-factor sign-in with recovery codes, new-device alerts, a session list with sign-out everywhere, e-mail verification, KYC for payouts.
- Forms and pages: every form carries a token (a stale one shows a 419 page), every echo is escaped, listing texts are stripped of tags, searches and sorts never reach the database as text, uploads are checked by content and stored under random names, PHP never runs under
uploads/, andconfig.php,data/,includes/and the page folders are not served (.htaccess). - Money: a payment exists only when the gateway reports it, twice-delivered callbacks count once, underpaid ones wait for staff, refunds claw the seller's share back, every move is in the double-entry ledger and rebuildable; escrow money never touches the marketplace.
- Fraud: ownership verification (DNS or registrar account), the risk score, auction flags, affiliate flags, reviews and badges, reports and bans.
- API and webhooks: keys with scopes and limits, signed deliveries, private-network addresses refused.
- Staff: roles and permissions, the audit trail of every change, 2FA expected for every staff account.
- Secrets: the install secret in
config.phpencrypts every stored key (gateways, registrars, SMS, push); logs mask them.
2. The Health & Security Check
Settings -> Health & Security Check runs the checklist on the live server and shows each row as green, orange or red with what to do:
| Group | Checks |
|---|---|
| Server | PHP version and its support date, extensions, OPcache, memory and upload limits, display_errors, disk space, writable folders, config.php permissions |
| Web | HTTPS, HSTS, the debug switch, the install secret, the proxy setting, and self-probes that fetch config.php, uploads/.htaccess, data/ and includes/ to prove they are not served |
| Accounts | demo accounts left over, staff without 2FA, how many super administrators, failed sign-ins and bans of the day |
| Application | the cron heartbeat, the job queue, mail, backups, the licence, payment gateways, log size, database size, version |
The daily cron job runs the same checks and sends staff a notification when something turns red (once per check per week). "Run the checks now" repeats them with the probes.
3. Going live, step by step
- Install over https, delete
install.php, set the site address with https. - Mail: SMTP and a test; Plugins: a payment gateway with its keys (test mode first, a real order, then live); Licence activated.
- The cron line every five minutes (Settings -> System shows it).
- Health check: everything green or understood. The usual orange rows on a new host: OPcache off (switch it on in the PHP options), HSTS off (switch it on once https works), demo accounts (delete them), staff without 2FA (each turns it on under My Account).
- The first backup, downloaded off the server; a restore tried once on a sub-domain.
- Pages and policies: Terms, Privacy, Cookie, Buyer and Seller agreements, Commission, Refund, Dispute, Auction terms, Transfer policy, KYC/AML, Trademark complaints (the pages exist under Content -> Pages with starter texts; the owner edits them for their jurisdiction).
4. Backups, updates, rollback
Backups (database + uploads) under Settings -> System, on demand or weekly by the cron; the update flow backs up, extracts the update zip, runs the tagged database steps once each, and can be rolled back by restoring the previous files and database. The update zip never carries config.php, data/, uploads/ or the installer.
5. Performance
The product caches what repeats (home sections, counts, rates, suggestions), paginates everything, resizes images at upload, sends mail and webhooks through the job queue, and keeps the search on indexed columns. On a normal host with OPcache a page costs 10 to 50 ms of its own work. The dev kit's load test (loadtest.php) measures throughput and latency and reads the per-page query counts from the profiler header; the operations guide has the 2.0.0 figures and how to repeat them on your server.