edheltzel

Preface

So in the past, I've used MAMP/MAMP Pro apps and others alike. I've also, setup my own local MAMP stack with homebrew, that used dnsmasq to dynamically add vhosts anytime I added a new folder to the Sites folder which made it very convenient. But, then I started running into other environment issues with PHP versions on remote machines/servers not being updated or some other crazy thingamabob breaking. I researched and invested time in Vagrant, but that seem to break more often than my homebrew setup. So I researched again investing time into Docker via Docker for Mac (which is BAMF), which I'm sold on and use daily, but it still seems a little bleeding edge and not so simple to wrap your head around the concept. Not to mention I don't have a real use case to play with and take advantage of all the features that come packed with Docker.

This is the beginning of trying to find something more simple, and slightly quicker to setup.

edheltzel

# -------------------------------------------------------------------
# This file live inside of your ~/.wp-cli
# -------------------------------------------------------------------

# path: cms  # this is the path to your WordPress files
core install:
  admin_user: <YOUR ADMIN USERNAME>
  admin_password: <YOUR ADMIN PASSWORD>
  admin_email: <YOUR ADMIN EMAIL>
  title: The Next Big Deal in WordPress Sites

edheltzel

How-to setup a simple git push deployment

These are my notes basically. At first i created this gist just as a reminder for myself. But feel free to use this for your project as a starting point. If you have questions you can find me on twitter @thomasf https://twitter.com/thomasf This is how i used it on a Debian Wheezy testing (https://www.debian.org/releases/testing/)

Discuss, ask questions, etc. here https://news.ycombinator.com/item?id=7445545

On the server (example.com)

edheltzel

RewriteEngine On
RewriteCond %{HTTP_REFERER} .*yelp.com.*$ [OR]
RewriteCond %{HTTP_REFERER} .*google.com.*$ [OR]
RewriteCond %{HTTP_REFERER} .*some_website.com.*$ [OR]
RewriteCond %{HTTP_REFERER} .*github.com.*$
RewriteRule ^(.*)$ http://your_site/custom_landing_page

edheltzel

ErrorDocument 404 /

RewriteEngine On 
RewriteBase / 
RewriteCond %{HTTP_HOST} ^([a-z0-9\-]+)\.domain\.com$  [NC]
RewriteCond %1 !^www$ [NC]
RewriteRule (.*) http://domain.com/%1 [R=301,L,NC]

edheltzel

Example: You have a branch refactor that is quite different from master. You can't merge all of the commits, or even every hunk in any single commit or master will break, but you have made a lot of improvements there that you would like to bring over to master.

Note: This will not preserve the original change authors. Only use if necessary, or if you don't mind losing that information, or if you are only merging your own work.

On master:

> git co -b temp

edheltzel

gem list | cut -d" " -f1 | sudo xargs gem uninstall -Iax

edheltzel

<?php 
// Function creates post duplicate as a draft and redirects then to the edit post screen

function rdm_duplicate_post_as_draft(){
	global $wpdb;
	if (! ( isset( $_GET['post']) || isset( $_POST['post'])  || ( isset($_REQUEST['action']) && 'rdm_duplicate_post_as_draft' == $_REQUEST['action'] ) ) ) {
		wp_die('No post to duplicate has been supplied!');
	}
 
	// get the original post id

edheltzel

<?php
/*-----------------------------------------------------------------------------------*/
/* UPDATE EMAIL ADDRESS FOR WORDPRESS
/* ----------------------------------------------------------------------------------*/
	// AUTO-DETECT THE SERVER
	function rdm_filter_wp_mail_from($email){
		// START OF CODE LIFTED FROM WORDPRESS CORE
		$sitename = strtolower( $_SERVER['SERVER_NAME'] );
		if ( substr( $sitename, 0, 4 ) == 'www.' ) {
			$sitename = substr( $sitename, 4 );

edheltzel

# Basic .htaccess file for postname permalinks
# Apache rewrite module must be enabled

# Rewrites / Permalinks
# =====================

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /