lukecav

wp db size
wp db size --tables
wp transient delete --expired
wp cache flush
wp post delete $(wp post list --post_type='revision' --format=ids)
wp comment delete $(wp comment list --status=spam --format=ids)
wp comment delete $(wp comment list --status=trash --format=ids)
wp db optimize

scriptingosx

#!/usr/bin/python

import sys
import plistlib
import subprocess
from Cocoa import NSBundle

if (len(sys.argv) == 2):
	model = sys.argv[1]
else:

mwpastore

README

This gist assumes you are migrating an existing site for www.example.com — ideally WordPress — to a new server — ideally Ubuntu Server 16.04 LTS — and wish to enable HTTP/2 (backwards compatibile with HTTP/1.1) with always-on HTTPS, caching, compression, and more. Although these instructions are geared towards WordPress, they should be trivially extensible to other PHP frameworks, other FastCGI backends, and even non-FastCGI backends (using proxy in lieu of fastcgi in the terminal Caddyfile stanza).

Quickstart: Use your own naked and canonical domain names instead of example.com and www.example.com and customize the Caddyfile and VCL provided in this gist to your preferences!

These instructions target Varnish Cache 4.1, PHP-FPM 7.0, and Caddy 0.10. (I'm using MariaDB 10.1 as well, but that's not relevant to this guide.)

itzikbenh

//Just a random file for loading your posts to see that the infinite scroll works. 
<?php get_header(); ?>

<div class="col-md-6 col-md-offset-3">
	<div class="post-container">
		<?php if ( have_posts() ) : while ( have_posts() ) : the_post(); ?>
			<div class="page-header post">
				<h1><?php the_title(); ?></h1>
				<p><?php the_excerpt(); ?></p>
			</div>