Deployment Requirements
A production Freehold CMS deployment needs more than compatible PHP syntax: it needs the documented directory boundary, HTTPS, database access, writable storage, email delivery and an operating plan.
Verify the changed business task after deployment
Record installed versions, apply changes in the documented order, run readiness checks, handle affected cache entries and test the public and administrative work that changed. Confirm sign-in, email, storage and provider communication when the release touches them.
Release checks
- HTTPS and correct document root.
- Compatible PHP and extensions.
- MySQL or MariaDB credentials.
- Protected private configuration.
- Writable storage with suitable permissions.
- Email and provider connectivity.
- Backup and rollback access.
Prepare the environment
Confirm the current PHP line and required extensions, MySQL or MariaDB compatibility, HTTPS, document root, private configuration and storage paths, outbound email and provider connectivity before installation.
Prepare the release path
Back up the database and files, record installed versions, apply changes in the documented order, run module readiness checks, clear or preload affected caches and test the public and administrative paths that changed.
Return to the developer overview
Use the technical index for architecture or custom-development planning.