pwenzel

.PHONY:  install

install: clean wordpress phpunit wp-cli
	git submodule init;
	@echo "\n\nNOTICE: You may need to configure a MySQL database for your Wordpress installation. Just run:"
	@echo " mysql -u root -p;"
	@echo " CREATE DATABASE example_site; \n"

wordpress: latest.tar.gz	
	tar -zxvf latest.tar.gz;

hofmannsven

WordPress Backups with WP-CLI

Avaq

const I  = x => x
const K  = x => y => x
const A  = f => x => f (x)
const T  = x => f => f (x)
const W  = f => x => f (x) (x)
const C  = f => y => x => f (x) (y)
const B  = f => g => x => f (g (x))
const S  = f => g => x => f (x) (g (x))
const S_ = f => g => x => f (g (x)) (x)
const S2 = f => g => h => x => f (g (x)) (h (x))

mgibbs189

<?php
$args = array(
    'post_type' => 'location',
    'posts_per_page' => -1,
    'order' => 'ASC',
    'orderby' => 'title',
    'facetwp' => true,
    'tax_query' => array(
        array(
            'taxonomy' => 'advertiser-level',

pudquick

brew is a bad neighbor

This isn't a guide about locking down homebrew so that it can't touch the rest of your system security-wise.

This guide doesn't fix the inherent security issues of a package management system that will literally yell at you if you try to do something about "huh, maybe it's not great my executables are writeable by my account without requiring authorization first".

But it absolutely is a guide about shoving it into its own little corner so that you can take it or leave it as you see fit, instead of just letting the project do what it likes like completely taking over permissions and ownership of a directory that might be in use by other software on your Mac and stomping all over their contents.

By following this guide you will:

• Never have to run sudo to forcefully change permissions of some directory to be owned by your account