If you last deployed a PHP site in the PHP 5 era, today’s requirements will feel stricter—and that is a good thing. Frameworks, Composer packages, and payment SDKs assume recent language features, HTTPS everywhere, and sane process limits. Whether you use HostPawa PHP hosting, general web hosting, or a VPS, use this checklist before you promise a go-live date.
1. Supported PHP versions
Modern apps should target actively supported PHP versions. Running end-of-life PHP exposes you to unpatched security issues and blocks Composer updates. Before ordering a plan:
- Check your framework’s supported PHP range (Laravel, Symfony, WordPress, custom apps)
- Confirm the host lets you select that version per site
- Plan upgrades: code that only runs on PHP 8.0 may need work for 8.3+
On HostPawa PHP hosting, choose the version that matches your composer.json platform config—not whatever the server default happens to be.
2. Extensions you will almost certainly need
Exact lists vary, but production PHP apps commonly require:
- pdo_mysql (or pdo_pgsql) for databases
- mbstring, intl for unicode and localisation
- openssl, curl for HTTPS APIs and webhooks
- json, xml, ctype, fileinfo
- bcmath or gmp for precise money maths
- zip for Composer and plugin installs
- redis or memcached when you use those cache backends
- gd or imagick for image processing
Ask for php -m output on a VPS, or check the panel’s PHP selector on shared hosting. Missing intl or curl is a frequent cause of “works on my laptop” failures.
3. Memory, execution time, and upload limits
Defaults that suit a brochure site will choke a reporting dashboard.
- memory_limit: 128M is tight for many Composer-era apps; 256M+ is common for admin-heavy tools
- max_execution_time: raise carefully for imports; prefer queues for long jobs
- upload_max_filesize / post_max_size: align with real user uploads (KYC docs, product images)
- opcache: enable in production for major speed wins
If you routinely hit limits on shared plans, either optimise the app or move heavy workloads to a VPS where you control php.ini.
4. Composer and deploy discipline
Modern PHP assumes Composer. Your hosting story should support:
- Deploying a built
vendor/directory, or running Composer on the server with SSH - Keeping
.envoutside web root / out of Git - Writable storage/cache directories with correct ownership
- Atomic releases (release folders + symlink) on VPS when uptime matters
Avoid editing production code over FTP as the primary workflow. It works in emergencies; it fails as a process.
5. HTTPS and mixed-content reality
Browsers, payment gateways, and OAuth providers expect HTTPS. Your host should make certificate issuance easy (Let’s Encrypt or equivalent). After SSL is on:
- Force HTTPS redirects
- Update canonical URLs and asset links
- Fix mixed content (HTTP images/scripts on HTTPS pages)
This applies equally on web hosting and VPS.
6. Cron, workers, and background work
Modern apps send email, call Paystack/Flutterwave webhooks, resize images, and generate PDFs. Those jobs should not block HTTP requests indefinitely.
- Confirm cron availability on shared hosting
- Use queue workers on VPS for sustained job processing
- Log failures somewhere you actually read
If the product roadmap includes lots of async work, budget for VPS early rather than fighting shared-hosting process limits.
7. Database and persistence
- MySQL/MariaDB with backups you can restore
- Separate DB users per app (least privilege)
- Charset/collation
utf8mb4for emoji and full Unicode - Remote DB access disabled unless required and firewalled
8. Observability and Nigeria-aware ops
At minimum: error logs, access logs, and disk alerts. Set application timezone to Africa/Lagos when serving local users. Peak traffic often lands in evenings—load-test reports and checkouts for those windows, not only quiet afternoons.
Shared PHP hosting vs VPS: requirements lens
Stay on shared / PHP hosting when: the app is request/response oriented, cron is enough, and memory fits the plan.
Move to VPS when: you need custom extensions, Redis, Supervisor, multiple runtimes, or guaranteed resources. HostPawa’s PHP hosting covers the managed path; VPS hosting covers the control path. Many teams begin on web hosting and upgrade when requirements harden.
Pre-flight checklist (copy/paste)
- PHP version matches Composer platform
- Required extensions present
- OPcache enabled
- HTTPS live and forced
- Document root points at
public/(for frameworks) - Storage directories writable
- Cron configured
- Backups tested once
- APP_DEBUG off in production
- Monitoring or log review habit in place
Bottom line
Modern PHP hosting is about versions, extensions, limits, HTTPS, and a sane background-job story—not just “Apache with PHP.” Validate those requirements on HostPawa PHP hosting or a VPS before launch, and you avoid the classic go-live scramble. When in doubt, start simple on web hosting and upgrade when the app’s architecture demands it.