OS X Screencast to animated GIF
This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.
Instructions
To capture the video (filesize: 19MB), using the free "QuickTime Player" application:
<?php | |
/* | |
* Plugin Name: Paulund WP List Table Example | |
* Description: An example of how to use the WP_List_Table class to display data in your WordPress Admin area | |
* Plugin URI: http://www.paulund.co.uk | |
* Author: Paul Underwood | |
* Author URI: http://www.paulund.co.uk | |
* Version: 1.0 | |
* License: GPL2 | |
*/ |
This playbook has been removed as it is now very outdated. |
# Managed WordPress Hosting .gitignore file for ignoring WordPress files | |
# | |
# Most recent revision here: | |
# https://gist.github.com/joemaller/4f7518e0d04a82a3ca16 | |
# | |
# Raw Source (for curl): | |
# https://gist.githubusercontent.com/joemaller/4f7518e0d04a82a3ca16/raw | |
# | |
# Used by these WordPress Development environments: | |
# https://github.com/ideasonpurpose/docker-wordpress-dev |
# remove php5 modules
apt-get autoremove --purge php5-*
# add php-7.0 source list by [Ondřej Surý](https://github.com/oerdnj)
add-apt-repository ppa:ondrej/php
# Update index
apt-get update
# Install php7.0-fpm with needed extensions
// jQuery.support.transition | |
// to verify that CSS3 transition is supported (or any of its browser-specific implementations) | |
$.support.transition = (function(){ | |
var thisBody = document.body || document.documentElement, | |
thisStyle = thisBody.style, | |
support = thisStyle.transition !== undefined || thisStyle.WebkitTransition !== undefined || thisStyle.MozTransition !== undefined || thisStyle.MsTransition !== undefined || thisStyle.OTransition !== undefined; | |
return support; | |
})(); |
Defining Eloquent model (will assume that DB table named is set as plural of class name and primary key named "id"):
class Shop extends Eloquent {}
Using custom table name
protected $table = 'my_shops';
<?php | |
array ( | |
'^wp-json/?$' => 'index.php?rest_route=/', | |
'^wp-json/(.*)?' => 'index.php?rest_route=/$matches[1]', | |
'^index.php/wp-json/?$' => 'index.php?rest_route=/', | |
'^index.php/wp-json/(.*)?' => 'index.php?rest_route=/$matches[1]', | |
'robots\\.txt$' => 'index.php?robots=1', | |
'.*wp-(atom|rdf|rss|rss2|feed|commentsrss2)\\.php$' => 'index.php?feed=old', | |
'.*wp-app\\.php(/.*)?$' => 'index.php?error=403', | |
'.*wp-register.php$' => 'index.php?register=true', |
As creating for the web has gotten more complex, build tools have become an essential part of my workflow. These tools are usually used to automate repetitive tasks such as pre-processing CSS stylesheets from Sass or Less, or compiling JavaScript from many smaller files. They can also reload browsers when files change -- not having to constantly mash reload is a significant productivity boost. Working without auto-refresh now feels like trying to type in mittens.
[Gulp][] and [Grunt][] run from the Terminal, [CodeKit][] and [LiveReload][] are standalone Mac apps. Gulp is relatively new, is very fast and its task definition files are written in JavaScript. Grunt is more established, works well and has a ton of people using it, but can be slower and requires a lot more configuration using verbose JSON files. CodeKit and LiveReload help with common workflows, Gulp and Grunt can do just about anything imaginable.
I’d been happily using Grunt for a while, but increasing buzz a
#!/bin/bash | |
# Add Vagrant's NFS setup commands to sudoers, for `vagrant up` without a password | |
# Updated to work with Vagrant 1.3.x | |
# Stage updated sudoers in a temporary file for syntax checking | |
TMP=$(mktemp -t vagrant_sudoers) | |
cat /etc/sudoers > $TMP | |
cat >> $TMP <<EOF | |
# Allow passwordless startup of Vagrant when using NFS. |