Knowledgebase

Deploying to Shared Hosting Print

  • devopsinfrastructure, devops, webhosting, cron, cpanel, caching, resourcelimits, permissions
  • 0

Practical constraints.

WHAT IS DIFFERENT

Limited or no terminal access No control over system packages Resource limits No persistent processes, typically

WHAT THAT RULES OUT

Some tooling Long-running workers Building on the server, frequently

WHAT WORKS WELL

Pulling from version control, where terminal access exists Deploying prebuilt artefacts Running tasks through cron

WHAT TO PREPARE LOCALLY

Compiled frontend assets Dependencies, if they cannot be installed on the server

WHAT TO SET UP ON CPANEL

The correct runtime version Cron entries, with full paths Directory structure keeping application files out of the public directory

WHAT TO AUTOMATE

The deployment steps, as a script run from the terminal.

WHAT TO CHECK AFTER EVERY DEPLOYMENT

Caches rebuilt Permissions correct Links to storage intact Scheduled tasks still configured

WHAT TO KEEP

The previous version, so reverting is possible.

WHAT TO DOCUMENT

The whole procedure.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot