PHP cPanel Deploys for Marketing Sites
A product marketing site is often WordPress on a cPanel host. That is enough when the job is a handoff, not a consumer binary. The deploy still needs a ritual. At Croncode we treat the English site like a store neighbor: if it dies, the badge still works, but the story and the quote path do not. This page is that ritual. When the site is the right object: when Elementor is enough.
A cPanel PHP deploy for a marketing site needs a backup, a staging copy, and a written owner. Fancy pipelines are optional. An overwritten wp-content on Friday is not a process.
What is the minimum release checklist?
- Backup files and the database before you touch production.
- Deploy to a staging subdomain that uses a copy of data, not live users.
- Click the store CTA and the contact path on a phone width.
- Confirm the privacy and support URLs that App Store Connect already cites.
- Write the person who can roll back tonight.
Store landers: landing pages. Support URLs: support email. Account owner: App Store account.
Which host habits break a Friday ship?
| Habit | Risk | Replace with |
|---|---|---|
| FTP a single plugin folder | Half-updated PHP | A full known set |
| Live editing Elementor on production | No rollback | Staging, then push |
| Shared admin with a contractor | Mystery users | Company emails. Security |
| No PHP version pin | White screen after host upgrade | Write the version |
Do not mix this host with the iOS repo secrets: same codebase risks. Handover the host in writing: handover.
When is cPanel the wrong deploy target?
When you need a signed-in consumer object, background jobs at app scale, or a store entitlement. Then you want custom software: custom software. Ecommerce that must move money: revenue. No-code limits: custom vs no-code.
Our apps stay on the App Store: YourStyle, Numira, Spylie, Luviport. The site introduces them. Catalog: what Croncode builds.
How does Istanbul overlap change a deploy?
Pick a window both sides can watch. Do not deploy at the start of a US holiday if the only rollback person is asleep in Europe/Istanbul. Hiring checks: Istanbul checklist. Shipping: how we ship. People: Goktug Unver, Yusufhan Sokur, Ozgur Ismet Ozkan.
What mistakes look like “just a marketing site”?
- No backup because “it is only WordPress”: the Journal and the quote form are the business card.
- Fake ranks in a hero after a plugin update: we will not. ASO: positioning.
- Analytics tags you cannot name: analytics.
- English-only after the app localized: onboarding localization.
Quote the host and the owner: quote packet. Hire: hire. Contact: contact. Journal: /en/journel/. Identity: Albuquerque LLC, not croncodetech.com. Identity.
What should a sprint demo show for a site increment?
The staging URL, then production after the window. Click the badge. Click contact. Show the backup timestamp. Demo standard: sprint demo. Content calendar: thirty-day plan. Design still QA’s the template on a small phone even if it is not SwiftUI.
What we will not do: ship a client site that claims we are another company, or a deploy with no owner. Will not build. Write the rollback command in the increment note: restore this backup ID, flush this cache, check this URL. If only one person can do that, you do not have a deploy. You have a hero. A lean studio can still write the note. The host panel is not an excuse to skip it.
Frequently asked questions
Do I need Git on cPanel?
Git helps. A dated backup and a staging copy matter more than the fashion of the pipeline.
Can I use a page builder and still deploy safely?
Yes if production is not the only copy. Builders make live-edit tempting. Resist it for launches.
What about email on the same cPanel?
Write who owns DNS and the mailbox. Support is a product surface. Do not let a host migration drop the address Apple shows.
Is this the same as shipping an iOS app?
No. Different store, different binary, different review. Same honesty: the live thing must match the promise.
Who rolls back at Croncode?
The person named on the increment note, usually design/web plus whoever has host access that week. Names start on the team pages.
