Complete these four steps in RunCloud before installing.
Recommended server size: 4 GB+ RAM. The CMS rebuilds the public CSS bundle on every page save, which needs ~1.5 GB of memory during the build. 1–2 GB hosts also work if you do all your editing on a local copy of the CMS and push compiled assets to the server via git — in that mode the server only serves files, never builds them.
1
Issue your SSL certificate
Go to your web app → SSL/TLS and issue a Let’s Encrypt certificate. The installer sets APP_URL to https:// — without SSL the redirect to the dashboard will fail.
2
Update PHP settings
Go to Server → PHP Settings and make two changes on that page:
(a) Memory Limit — set to 512M. The page editor parses large blade templates in memory; the default 256M is too tight.
(b) Disabled Functions — replace the entire list with the one below. This removes the functions WebProCMS requires (proc_open, set_time_limit, ignore_user_abort, tmpfile) while keeping dangerous ones blocked.
3
Raise the LSPHP memory limit
Edit your app’s OpenLiteSpeed Web Application Config, find the extprocessor block, and change both memSoftLimit and memHardLimit from 2047M to either 3072M or 4096M. The Node build that recompiles CSS on every page save needs more virtual address space than the 2 GB default allows. 3 GB is the minimum that lets the build finish; 4 GB (shown below) leaves plenty of headroom for the rest of the site to keep serving requests while the build is running. Click Save and let OLS reload.
4
Add a deployment script and redeploy
Go to your web app → Deployment and paste the script below into the deployment script box. Then hit Deploy — this pulls the latest code, installs Composer dependencies, runs any new migrations, rebuilds the caches, builds the frontend assets, and clears the response cache. Once it finishes, return here and fill out the form below.
Fill in your site details below to generate your .env file, run migrations, and create your admin account.