Setting up Digital Ocean for WordPress

Digital Ocean provide great deals on a variety of VPS options to power your WordPress website. Prices start from $5pcm for a 500MB VPS.

One of the great things about Digital Ocean is that the servers are up and running within a minute, but also – they use very good hardware. Every server uses a RAID SSD array, has a 1Gb network connection and comes with the option of deploying a wide variety of operating systems.

They offer 1-click installs, but below I’m outlining a custom install so you can configure Digital Ocean for MAXIMUM performance – we want very fast speed but we also want humungous numbers of simultaneous users to be possible.

Choose your ‘Droplet’

Go for whatever you like – the more the better. I’d recommend a minimum of 1GB RAM which is currently $10pcm.

You can view configuration and pricing options here. (this affiliate link gets you $10 discount)

Make sure you install Ubuntu if you want to follow this guide.

You’ll be emailed a username and password. Download Putty, and connect to your server by entering the IP address that Digital Ocean provide you. Enter your username and password and you’ll be on your server. You’ll end up on a black screen where you can enter the commands below – this is you on your server.

(optional) Set up SFTP

Run the following command:

apt-get install vsftpd

Configure FTP as per this FTP set up guide

You will now be able to connect to your server using SFTP (I prefer Filezilla as my FTP client)

A good practice is to set up a specific user for FTP and give them the primary group of www-data so that files are automatically allocated the correct group.

<pre class="bash">useradd -G www-data ftpuser
passwd ftpuser

Install NginX, PHP5-FPM, MySQL and additional PHP libraries required for WordPress

Run the following commands:

apt-get update
apt-get install nginx
apt-get install mysql-server
mysql_install_db
mysql_secure_installation
apt-get install php5-fpm php5-mysql
apt-get install php5-curl
apt-get install php5-gd
mkdir /var/www
chmod 775 /var/www
chown www-data:www-data /var/www
cd /var/www
wget http://wordpress.org/latest.tar.gz
tar -xzvf latest.tar.gz
mv wordpress sitefoldername<-- rename the wordpress folder to something representing your website
mysql -u root -p

create database sitename;
grant all privileges on sitename.* to "siteusername"@"localhost" identified by "sitedbpassword";
exit

Set up your DNS to point a domain at your server. If you’re using GoDaddy then point @ and www both at your new IP address.

If you were to access your site now, you would see the following:

Configure your files

This is where we’ll set up nginx to perform well and to point at your new files so you can complete the wordpress set up.

The first file to modify is /etc/nginx/nginx.conf. Run the following two commands to figure out two of the most important settings:

cat /proc/cpuinfo | grep processor | wc -l # use the number from this for your <em>worker_processes</em> setting
ulimit -n # use the number from this for <em>worker_connections</em> setting

Switching from Sockets to TCP

The other setting I typically change is to switch from sockets to TCP IP as demonstrated in the following files:

/etc/nginx/nginx.conf high performance example

This file has all the great settings you’ll want for WordPress – using gzip for static file compression etc. Just change your worker_processes and worker_connections values according to the commands you ran above and it should be good to go. For best results, compare the file with your existing file and change line by line so you get to know your config files

user www-data;

# As a thumb rule: One per CPU. If you are serving a large amount
# of static files, which requires blocking disk reads, you may want
# to increase this from the number of cpu_cores available on your
# system.
#
# The maximum number of connections for Nginx is calculated by:
# max_clients = worker_processes * worker_connections
worker_processes 1;

# Maximum file descriptors that can be opened per process
# This should be > worker_connections
worker_rlimit_nofile 8192;

events {
# When you need > 8000 * cpu_cores connections, you start optimizing
# your OS, and this is probably the point at where you hire people
# who are smarter than you, this is *a lot* of requests.
worker_connections 500;
}

error_log /var/log/nginx/error.log;

pid /var/run/nginx.pid;

http {
charset utf-8;

# Set the mime-types via the mime.types external file
include mime.types;

# And the fallback mime-type
default_type application/octet-stream;

# Click tracking!
access_log /var/log/nginx/access.log;

# Hide nginx version
server_tokens off;

# ~2 seconds is often enough for HTML/CSS, but connections in
# Nginx are cheap, so generally it's safe to increase it
keepalive_timeout 20;

# You usually want to serve static files with Nginx
sendfile on;

tcp_nopush on; # off may be better for Comet/long-poll stuff
tcp_nodelay off; # on may be better for Comet/long-poll stuff

server_name_in_redirect off;
types_hash_max_size 2048;

gzip on;
gzip_http_version 1.0;
gzip_comp_level 5;
gzip_min_length 512;
gzip_buffers 4 8k;
gzip_proxied any;
gzip_types
# text/html is always compressed by HttpGzipModule
text/css
text/plain
text/x-component
application/javascript
application/json
application/xml
application/xhtml+xml
application/x-font-ttf
application/x-font-opentype
application/vnd.ms-fontobject
image/svg+xml
image/x-icon;

# This should be turned on if you are going to have pre-compressed copies (.gz) of
# static files available. If not it should be left off as it will cause extra I/O
# for the check. It would be better to enable this in a location {} block for
# a specific directory:
# gzip_static on;

gzip_disable "msie6";
gzip_vary on;

# Upstream to abstract backend connection(s) for PHP
upstream php {
server 127.0.0.1:7777;
# server unix:/run/php-fpm/php-fpm.sock;
}

include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;
}

/etc/php5/fpm/pool.d/www.conf high performance example

This file has TCP enabled too, rather than sockets. It also has pm.max_requests = 500 which refreshes the php5-fpm process after 500 requests which is good practice in case you have any memory-leaky WordPress plugins and will significantly improve uptime and performance.

The only value you really need to configure yourself in this file is pm.max_children = 50. If you have less than 2GB RAM you should reduce this. e.g. on a 500MB VPS you should probably set pm.max_children = 5, on a 1GB machine you could go for pm.max_children = 20. The actual values vary depending on how much memory each of your php5-fpm processes are using when they’re actively serving up pages. This will depend on how many plugins you have in WordPress as well as the size of your pages. The above are good guides though and should serve you very well.

; Start a new pool named 'www'.
; the variable $pool can we used in any directive and will be replaced by the
; pool name ('www' here)
[www]

; Per pool prefix
; It only applies on the following directives:
; - 'slowlog'
; - 'listen' (unixsocket)
; - 'chroot'
; - 'chdir'
; - 'php_values'
; - 'php_admin_values'
; When not set, the global prefix (or /usr) applies instead.
; Note: This directive can also be relative to the global prefix.
; Default Value: none
;prefix = /path/to/pools/$pool

; Unix user/group of processes
; Note: The user is mandatory. If the group is not set, the default user's group
; will be used.
user = www-data
group = www-data

; The address on which to accept FastCGI requests.
; Valid syntaxes are:
; 'ip.add.re.ss:port' - to listen on a TCP socket to a specific address on
; a specific port;
; 'port' - to listen on a TCP socket to all addresses on a
; specific port;
; '/path/to/unix/socket' - to listen on a unix socket.
; Note: This value is mandatory.
;listen = /var/run/php5-fpm.sock
listen = 127.0.0.1:7777;

; Set listen(2) backlog.
; Default Value: 65535 (-1 on FreeBSD and OpenBSD)
;listen.backlog = 65535

; Set permissions for unix socket, if one is used. In Linux, read/write
; permissions must be set in order to allow connections from a web server. Many
; BSD-derived systems allow connections regardless of permissions.
; Default Values: user and group are set as the running user
; mode is set to 0660
listen.owner = www-data
listen.group = www-data
;listen.mode = 0660

; List of ipv4 addresses of FastCGI clients which are allowed to connect.
; Equivalent to the FCGI_WEB_SERVER_ADDRS environment variable in the original
; PHP FCGI (5.2.2+). Makes sense only with a tcp listening socket. Each address
; must be separated by a comma. If this value is left blank, connections will be
; accepted from any ip address.
; Default Value: any
listen.allowed_clients = 127.0.0.1

; Specify the nice(2) priority to apply to the pool processes (only if set)
; The value can vary from -19 (highest priority) to 20 (lower priority)
; Note: - It will only work if the FPM master process is launched as root
; - The pool processes will inherit the master process priority
; unless it specified otherwise
; Default Value: no set
; priority = -19

; Choose how the process manager will control the number of child processes.
; Possible Values:
; static - a fixed number (pm.max_children) of child processes;
; dynamic - the number of child processes are set dynamically based on the
; following directives. With this process management, there will be
; always at least 1 children.
; pm.max_children - the maximum number of children that can
; be alive at the same time.
; pm.start_servers - the number of children created on startup.
; pm.min_spare_servers - the minimum number of children in 'idle'
; state (waiting to process). If the number
; of 'idle' processes is less than this
; number then some children will be created.
; pm.max_spare_servers - the maximum number of children in 'idle'
; state (waiting to process). If the number
; of 'idle' processes is greater than this
; number then some children will be killed.
; ondemand - no children are created at startup. Children will be forked when
; new requests will connect. The following parameter are used:
; pm.max_children - the maximum number of children that
; can be alive at the same time.
; pm.process_idle_timeout - The number of seconds after which
; an idle process will be killed.
; Note: This value is mandatory.
pm = dynamic

; The number of child processes to be created when pm is set to 'static' and the
; maximum number of child processes when pm is set to 'dynamic' or 'ondemand'.
; This value sets the limit on the number of simultaneous requests that will be
; served. Equivalent to the ApacheMaxClients directive with mpm_prefork.
; Equivalent to the PHP_FCGI_CHILDREN environment variable in the original PHP
; CGI. The below defaults are based on a server without much resources. Don't
; forget to tweak pm.* to fit your needs.
; Note: Used when pm is set to 'static', 'dynamic' or 'ondemand'
; Note: This value is mandatory.
pm.max_children = 50

; The number of child processes created on startup.
; Note: Used only when pm is set to 'dynamic'
; Default Value: min_spare_servers + (max_spare_servers - min_spare_servers) / 2
pm.start_servers = 2

; The desired minimum number of idle server processes.
; Note: Used only when pm is set to 'dynamic'
; Note: Mandatory when pm is set to 'dynamic'
pm.min_spare_servers = 1

; The desired maximum number of idle server processes.
; Note: Used only when pm is set to 'dynamic'
; Note: Mandatory when pm is set to 'dynamic'
pm.max_spare_servers = 3

; The number of seconds after which an idle process will be killed.
; Note: Used only when pm is set to 'ondemand'
; Default Value: 10s
;pm.process_idle_timeout = 10s;

; The number of requests each child process should execute before respawning.
; This can be useful to work around memory leaks in 3rd party libraries. For
; endless request processing specify '0'. Equivalent to PHP_FCGI_MAX_REQUESTS.
; Default Value: 0
pm.max_requests = 500

; The URI to view the FPM status page. If this value is not set, no URI will be
; recognized as a status page. It shows the following informations:
; pool - the name of the pool;
; process manager - static, dynamic or ondemand;
; start time - the date and time FPM has started;
; start since - number of seconds since FPM has started;
; accepted conn - the number of request accepted by the pool;
; listen queue - the number of request in the queue of pending
; connections (see backlog in listen(2));
; max listen queue - the maximum number of requests in the queue
; of pending connections since FPM has started;
; listen queue len - the size of the socket queue of pending connections;
; idle processes - the number of idle processes;
; active processes - the number of active processes;
; total processes - the number of idle + active processes;
; max active processes - the maximum number of active processes since FPM
; has started;
; max children reached - number of times, the process limit has been reached,
; when pm tries to start more children (works only for
; pm 'dynamic' and 'ondemand');
; Value are updated in real time.
; Example output:
; pool: www
; process manager: static
; start time: 01/Jul/2011:17:53:49 +0200
; start since: 62636
; accepted conn: 190460
; listen queue: 0
; max listen queue: 1
; listen queue len: 42
; idle processes: 4
; active processes: 11
; total processes: 15
; max active processes: 12
; max children reached: 0
;
; By default the status page output is formatted as text/plain. Passing either
; 'html', 'xml' or 'json' in the query string will return the corresponding
; output syntax. Example:
; http://www.foo.bar/status
; http://www.foo.bar/status?json
; http://www.foo.bar/status?html
; http://www.foo.bar/status?xml
;
; By default the status page only outputs short status. Passing 'full' in the
; query string will also return status for each pool process.
; Example:
; http://www.foo.bar/status?full
; http://www.foo.bar/status?json&full
; http://www.foo.bar/status?html&full
; http://www.foo.bar/status?xml&full
; The Full status returns for each process:
; pid - the PID of the process;
; state - the state of the process (Idle, Running, ...);
; start time - the date and time the process has started;
; start since - the number of seconds since the process has started;
; requests - the number of requests the process has served;
; request duration - the duration in µs of the requests;
; request method - the request method (GET, POST, ...);
; request URI - the request URI with the query string;
; content length - the content length of the request (only with POST);
; user - the user (PHP_AUTH_USER) (or '-' if not set);
; script - the main script called (or '-' if not set);
; last request cpu - the %cpu the last request consumed
; it's always 0 if the process is not in Idle state
; because CPU calculation is done when the request
; processing has terminated;
; last request memory - the max amount of memory the last request consumed
; it's always 0 if the process is not in Idle state
; because memory calculation is done when the request
; processing has terminated;
; If the process is in Idle state, then informations are related to the
; last request the process has served. Otherwise informations are related to
; the current request being served.
; Example output:
; ************************
; pid: 31330
; state: Running
; start time: 01/Jul/2011:17:53:49 +0200
; start since: 63087
; requests: 12808
; request duration: 1250261
; request method: GET
; request URI: /test_mem.php?N=10000
; content length: 0
; user: -
; script: /home/fat/web/docs/php/test_mem.php
; last request cpu: 0.00
; last request memory: 0
;
; Note: There is a real-time FPM status monitoring sample web page available
; It's available in: ${prefix}/share/fpm/status.html
;
; Note: The value must start with a leading slash (/). The value can be
; anything, but it may not be a good idea to use the .php extension or it
; may conflict with a real PHP file.
; Default Value: not set
;pm.status_path = /status

; The ping URI to call the monitoring page of FPM. If this value is not set, no
; URI will be recognized as a ping page. This could be used to test from outside
; that FPM is alive and responding, or to
; - create a graph of FPM availability (rrd or such);
; - remove a server from a group if it is not responding (load balancing);
; - trigger alerts for the operating team (24/7).
; Note: The value must start with a leading slash (/). The value can be
; anything, but it may not be a good idea to use the .php extension or it
; may conflict with a real PHP file.
; Default Value: not set
;ping.path = /ping

; This directive may be used to customize the response of a ping request. The
; response is formatted as text/plain with a 200 response code.
; Default Value: pong
;ping.response = pong

; The access log file
; Default: not set
;access.log = log/$pool.access.log

; The access log format.
; The following syntax is allowed
; %%: the '%' character
; %C: %CPU used by the request
; it can accept the following format:
; - %{user}C for user CPU only
; - %{system}C for system CPU only
; - %{total}C for user + system CPU (default)
; %d: time taken to serve the request
; it can accept the following format:
; - %{seconds}d (default)
; - %{miliseconds}d
; - %{mili}d
; - %{microseconds}d
; - %{micro}d
; %e: an environment variable (same as $_ENV or $_SERVER)
; it must be associated with embraces to specify the name of the env
; variable. Some exemples:
; - server specifics like: %{REQUEST_METHOD}e or %{SERVER_PROTOCOL}e
; - HTTP headers like: %{HTTP_HOST}e or %{HTTP_USER_AGENT}e
; %f: script filename
; %l: content-length of the request (for POST request only)
; %m: request method
; %M: peak of memory allocated by PHP
; it can accept the following format:
; - %{bytes}M (default)
; - %{kilobytes}M
; - %{kilo}M
; - %{megabytes}M
; - %{mega}M
; %n: pool name
; %o: output header
; it must be associated with embraces to specify the name of the header:
; - %{Content-Type}o
; - %{X-Powered-By}o
; - %{Transfert-Encoding}o
; - ....
; %p: PID of the child that serviced the request
; %P: PID of the parent of the child that serviced the request
; %q: the query string
; %Q: the '?' character if query string exists
; %r: the request URI (without the query string, see %q and %Q)
; %R: remote IP address
; %s: status (response code)
; %t: server time the request was received
; it can accept a strftime(3) format:
; %d/%b/%Y:%H:%M:%S %z (default)
; %T: time the log has been written (the request has finished)
; it can accept a strftime(3) format:
; %d/%b/%Y:%H:%M:%S %z (default)
; %u: remote user
;
; Default: "%R - %u %t \"%m %r\" %s"
;access.format = "%R - %u %t \"%m %r%Q%q\" %s %f %{mili}d %{kilo}M %C%%"

; The log file for slow requests
; Default Value: not set
; Note: slowlog is mandatory if request_slowlog_timeout is set
;slowlog = log/$pool.log.slow

; The timeout for serving a single request after which a PHP backtrace will be
; dumped to the 'slowlog' file. A value of '0s' means 'off'.
; Available units: s(econds)(default), m(inutes), h(ours), or d(ays)
; Default Value: 0
;request_slowlog_timeout = 0

; The timeout for serving a single request after which the worker process will
; be killed. This option should be used when the 'max_execution_time' ini option
; does not stop script execution for some reason. A value of '0' means 'off'.
; Available units: s(econds)(default), m(inutes), h(ours), or d(ays)
; Default Value: 0
;request_terminate_timeout = 0

; Set open file descriptor rlimit.
; Default Value: system defined value
;rlimit_files = 1024

; Set max core size rlimit.
; Possible Values: 'unlimited' or an integer greater or equal to 0
; Default Value: system defined value
;rlimit_core = 0

; Chroot to this directory at the start. This value must be defined as an
; absolute path. When this value is not set, chroot is not used.
; Note: you can prefix with '$prefix' to chroot to the pool prefix or one
; of its subdirectories. If the pool prefix is not set, the global prefix
; will be used instead.
; Note: chrooting is a great security feature and should be used whenever
; possible. However, all PHP paths will be relative to the chroot
; (error_log, sessions.save_path, ...).
; Default Value: not set
;chroot =

; Chdir to this directory at the start.
; Note: relative path can be used.
; Default Value: current directory or / when chroot
chdir = /

; Redirect worker stdout and stderr into main error log. If not set, stdout and
; stderr will be redirected to /dev/null according to FastCGI specs.
; Note: on highloaded environement, this can cause some delay in the page
; process time (several ms).
; Default Value: no
;catch_workers_output = yes

; Limits the extensions of the main script FPM will allow to parse. This can
; prevent configuration mistakes on the web server side. You should only limit
; FPM to .php extensions to prevent malicious users to use other extensions to
; exectute php code.
; Note: set an empty value to allow all extensions.
; Default Value: .php
;security.limit_extensions = .php .php3 .php4 .php5

; Pass environment variables like LD_LIBRARY_PATH. All $VARIABLEs are taken from
; the current environment.
; Default Value: clean env
;env[HOSTNAME] = $HOSTNAME
;env[PATH] = /usr/local/bin:/usr/bin:/bin
;env[TMP] = /tmp
;env[TMPDIR] = /tmp
;env[TEMP] = /tmp

; Additional php.ini defines, specific to this pool of workers. These settings
; overwrite the values previously defined in the php.ini. The directives are the
; same as the PHP SAPI:
; php_value/php_flag - you can set classic ini defines which can
; be overwritten from PHP call 'ini_set'.
; php_admin_value/php_admin_flag - these directives won't be overwritten by
; PHP call 'ini_set'
; For php_*flag, valid values are on, off, 1, 0, true, false, yes or no.

; Defining 'extension' will load the corresponding shared extension from
; extension_dir. Defining 'disable_functions' or 'disable_classes' will not
; overwrite previously defined php.ini values, but will append the new value
; instead.

; Note: path INI options can be relative and will be expanded with the prefix
; (pool, global or /usr)

; Default Value: nothing is defined by default except the values in php.ini and
; specified at startup with the -d argument
;php_admin_value[sendmail_path] = /usr/sbin/sendmail -t -i -f [email protected]
;php_flag[display_errors] = off
;php_admin_value[error_log] = /var/log/fpm-php.www.log
;php_admin_flag[log_errors] = on
;php_admin_value[memory_limit] = 32M

Create a Global WordPress.conf file

This makes setting up more than one website on your VPS a lot easier and makes any maintenance changes easier too (e.g. switching between sockets and TCP connections)

I recommend you create this in /etc/nginx/wordpress.conf. This really helps when you have multiple websites on your VPS since they will all just use the configuration from here.

# Try static files first, then php
index index.html index.htm index.php;
gzip on;
gzip_disable "msie6";
gzip_types text/plain text/css application/javascript application/x-javascript text/javascript application/json text/xml application/xml application/xml+rss;
# Specify a character set
charset utf-8;

# Redirect needed to "hide" index.php
location / {
try_files $uri $uri/ /index.php?q=$uri&$args;
}
# Don't log robots.txt or favicon.ico files
location = /favicon.ico { log_not_found off; access_log off; }
location = /robots.txt { access_log off; log_not_found off; }

# 404 errors handled by our application, for instance Laravel or CodeIgniter
error_page 404 /index.php;

# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
location ~ \.php$ {
fastcgi_split_path_info ^(.+\.php)(/.+)$;
# NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini
fastcgi_pass 127.0.0.1:7777;
# fastcgi_pass unix:/var/run/php5-fpm.sock;
fastcgi_index index.php;
include fastcgi_params;
}
location ~* \.(jpg|jpeg|gif|png|css|js|ico|xml|html)$ {
access_log off;
log_not_found off;
expires 360d;
}

location ~ ^/(status|ping)$ {
access_log off;
allow 127.0.0.1;
deny all;
include fastcgi_params;
fastcgi_pass 127.0.0.1:7777;
# fastcgi_pass unix:/var/run/php5-fpm.sock;
}
# Deny access to .htaccess
location ~ /\.ht {
deny all;
}

Per Site Configuration /etc/nginx/sites-available/default

This is the file you edit to add each website domain/Wordpress install. You basically add one server {…} tag for each website you are hosting on your VPS. Note how we include the wordpress.conf file. Don’t be confused by the location of wordpress.conf – if you simply state include wordpress.conf it will look for it in the /etc/nginx folder rather than the /etc/nginx/sites-available folder as you may expect.

You need to configure your web root, access_log, error_log and server_name – see the comments in the script.

server {
# Document root
root /var/www/sitename; # where are your web files stored for this website

# Specific logs for this vhost
access_log /var/log/nginx/sitename.com-access.log; #where will access logs be stored
error_log /var/log/nginx/sitename.com-error.log error; #where will error logs be stored

server_name sitename.affiliatewebdesigners.com; # which web address is this for (in this example I have a subdomain but you can do www.example.com)

include wordpress.conf; # include the wordpress.conf file we made earlier - this has all the settings required to use php5-fpm and all the compression settings etc - using this include saves us repeating all of that config for evey site we add
}

server {
# add another site by repeating another server block
}

Another alternative to the above is to create separate files for each website. If you do this, you’ll need this command to link the relevant file through to the /etc/nginx/sites-enabled/ folder:

<pre>ln -s /etc/nginx/sites-available/example.com /etc/nginx/sites-enabled/example.com</pre>

So, that’s it. Once you have all of these files set up, run the following commands to restart the relevant services. Presuming you have a WordPress website in your root folder, then your website will now be running on Apache. (If you were modifying an existing server, you did remember to remove Apache right? That old memory hog should never be allowed near a WordPress site again)

service nginx restart
service php5-fpm restart

Troubleshooting

Some additional things you can set up:

Modify /etc/php5/fpm/pool.d/www.conf to output php5-fpm errors:

<pre><code>; Redirect worker stdout and stderr into main error log. If not set, stdout and
; stderr will be redirected to /dev/null according to FastCGI specs.
; Default Value: no
catch_workers_output = yes

View errors by running:

tail /var/log/php5-fpm.log
tail /var/log/nginx/[there are a variety of log files in this folder]

If PHP5-FPM fails to start the most likely problem from the above – you can check errors by running PHP5-FPM in foreground mode:

<pre><code>php5-fpm -y /etc/php5/fpm/php-fpm.conf
</code>

If you have any questions or comments, let me know below.

• Author
• Recent Posts

Chat to me

Dave Hilditch

Founder at Affiliate Web Designers

Dave has been programming since 6 years old and has been developing WordPress plugins, themes and websites since 2010. In the past he built the browse view technology for Skyscanner and now he helps clients with interesting website challenges.

He is always on at least one of his computers when he's awake, so get in touch and he'll get right back to you.

Chat to me

Latest posts by Dave Hilditch (see all)

• My WordPress performance plugins and server stack have moved - July 31, 2016
• Price Comparison Pro 1.2 Released - July 5, 2016
• How to run backups on huge WordPress websites without your website being brought offline - February 4, 2016