Dan Knauss dknauss

FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.

Effective Engineer - Notes

By Edmond Lau
Highly Recommended 👍
http://www.theeffectiveengineer.com/

What's an Effective Engineer?

Setting up a WordPress site on AWS

This tutorial walks through setting up AWS infrastructure for WordPress, starting at creating an AWS account. We'll manually provision a single EC2 instance (i.e an AWS virtual machine) to run WordPress using Nginx, PHP-FPM, and MySQL.

This tutorial assumes you're relatively comfortable on the command line and editing system configuration files. It is intended for folks who want a high-level of control and understanding of their infrastructure. It will take about half an hour if you don't Google away at some point.

If you experience any difficulties or have any feedback, leave a comment. 🐬

Coming soon: I'll write another tutorial on a high availability setup for WordPress on AWS, including load-balancing multiple application servers in an auto-scaling group and utilizing RDS.

Important Notice for WordPress Plugins Using PHP 4 Style Constructors

The ability to use PHP 4 style constructors is getting removed from PHP. Without an update, many plugins will eventually no longer work (this is PHP breaking this backwards compatibility, not WordPress)

One of the more common uses of the PHP 4 style constructor (as opposed to PHP 5 style __construct() ) are plugins with widgets calling WP_Widget::WP_Widget() and/or parent::WP_Widget() and/or {object}->WP_Widget()

Note: Starting in WordPress 4.3, regardless of the PHP version in use on a server, WordPress will throw a deprecated notice when one of the PHP 4 style constructors is called specifically for widgets.

Basically instead of doing these:

	<?php
	// PHP memory limit for this site
	define( 'WP_MEMORY_LIMIT', '128M' );
	define( 'WP_MAX_MEMORY_LIMIT', '256M' ); // Increase admin-side memory limit.

	// Database
	define( 'WP_ALLOW_REPAIR', true ); // Allow WordPress to automatically repair your database.
	define( 'DO_NOT_UPGRADE_GLOBAL_TABLES', true ); // Don't make database upgrades on global tables (like users)

	// Explicitely setting url

	<?php
	// pick a hook from the wp-login.php file that best our needs. I chose the filter: wp_login_errors
	add_filter( 'wp_login_errors', 'my_login_form_lock_down', 90, 2 );

	/**
	* Completely lock down the WordPress login form by hijacking the page
	* and only executing the the login header, footer, and necessary
	* closing tags.
	*
	* Provide a secret way to show the login form as a url variable in

	# This is a template .gitignore file for git-managed WordPress projects.
	#
	# Fact: you don't want WordPress core files, or your server-specific
	# configuration files etc., in your project's repository. You just don't.
	#
	# Solution: stick this file up your repository root (which it assumes is
	# also the WordPress root directory) and add exceptions for any plugins,
	# themes, and other directories that should be under version control.
	#
	# See the comments below for more info on how to add exceptions for your

	/**
	* Auto Complete all WooCommerce orders.
	*/
	add_action( 'woocommerce_thankyou', 'custom_woocommerce_auto_complete_order' );
	function custom_woocommerce_auto_complete_order( $order_id ) {
	if ( ! $order_id ) {
	return;
	}

	$order = wc_get_order( $order_id );

	add_action( 'woocommerce_cart_actions', 'move_proceed_button' );
	function move_proceed_button( $checkout ) {
	echo '<a href="' . esc_url( WC()->cart->get_checkout_url() ) . '" class="checkout-button button alt wc-forward" >' . __( 'Proceed to Checkout', 'woocommerce' ) . '</a>';
	}

	add_action( 'woocommerce_before_cart', 'move_proceed_button' );
	function move_proceed_button( $checkout ) {
	echo '<a href="' . esc_url( WC()->cart->get_checkout_url() ) . '" class="checkout-button button alt wc-forward" >' . __( 'Proceed to Checkout', 'woocommerce' ) . '</a>';
	}