WPCloud Deploy Documentation

Requirements

Using WP CLOUD DEPLOY to deploy WordPress Servers and Sites requires the following: An existing WordPress site where you can install the plugin That site needs to meet the following requirements:

  • WordPress 5.4 or later
  • PHP 7.x
  • WP CRON enabled and working
  • Ubuntu 18.04 or later (recommended)

View more information about requirements

PHP Configuration Tweaks

The PHP configuration for the server on which WPCloud Deploy is installed will need some tweaks to handle long running PHP processes:

  • Increase your php_max_execution_time to at least 180 seconds or, better yet, 300 seconds.

You will NOT be able to deploy a server unless this task is completed!

Web Server Configuration Tweaks

The webserver on which WPCloud Deploy is installed might need some tweaks to handle long running processes.  If you are seeing strange behavior then you will need to adjust the following settings:

FOR NGINX:
    Set your fastcgi_read_timeoutclient_header_timeout and client_body_timeout values in your nginx configuration file to 600 seconds or more.
FOR NGINX used as a proxy in front of an APACHE server:
    Set your proxy_read_timeout value in your nginx configuration file to 600 seconds or more.
FOR APACHE Servers:
    Set your TimeOut value in your .htaccess file to 600 seconds or more.

Other Server Checks.

Finally please verify that the LibSodium library is installed on the linux server.  Most Ubuntu installations already have this library installed but some other servers might not have it.  LibSodium is used by the PHP process that securely connects to your server over SSH.

Local Installations

You cannot use a WordPress installation that is on your personal computer. This is because servers need to call back into the plugin in order to update it of the status of operations. Most local installations are not accessible from the internet, are behind firewalls or do not have public DNS records.

WP CRON

We strongly suggest that you use a LINUX cron and disable WP CRON.  This is because WP CRON only fires if the site has traffic and chances are, the site you’re running this on will not have a lot of traffic.  Set your LINUX CRON to a 1 minute interval. If you do decide to use the native WP CRON process, it is very important that you make sure it is working and firing every 1 minute.  This is because we use the CRON process to poll the server in order to figure out the status of operations and when operations are completed as well as to pull log files and submit new commands as needed. You will get some very very strange behavior and long delays if your WP CRON process isn’t firing very often!

Share: