In your command-line run the following commands:
brew doctor
brew update
In your command-line run the following commands:
brew doctor
brew update
if [ -L $0 ] ; then | |
BASEDIR=$(cd "$(dirname "$(readlink $0)")"; pwd -P) # for symbolic link | |
else | |
BASEDIR=$(cd "$(dirname "$0")"; pwd -P) # for normal file | |
fi |
The following will guide you through the process of enabling SSL on a Apache webserver
Create a directory within /etc/apache2/
using Terminal.app: sudo mkdir /etc/apache2/ssl
Next, generate two host keys:
These instructions will guide you through the process of setting up local, trusted websites on your own computer.
These instructions are intended to be used on macOS Sierra, but they have been known to work in El Capitan, Yosemite, Mavericks, and Mountain Lion.
NOTE: You may substitute the edit
command for nano
, vim
, or whatever the editor of your choice is. Personally, I forward the edit
command to Sublime Text:
alias edit="/Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl"
<!DOCTYPE html> | |
<html> | |
<head> | |
<meta charset="utf-8" /> | |
<title>Virtual Scrolling Demo</title> | |
<style> | |
html, body { | |
width: 100%; | |
height: 100%; | |
margin: 0; |
require 'capistrano/setup' | |
require 'capistrano/deploy' | |
require 'capistrano/scm' | |
require 'capistrano/git' | |
class Capistrano::Git < Capistrano::SCM | |
module SubmoduleStrategy | |
include DefaultStrategy | |
def release |
On the Refinery29 Mobile Web Team, codenamed "Bicycle", all of our unit tests are written using Jasmine, an awesome BDD library written by Pivotal Labs. We recently switched how we set up data for tests from declaring and assigning to closures, to assigning properties to each test case's this
object, and we've seen some awesome benefits from doing such.
Up until recently, a typical unit test for us looked something like this:
describe('views.Card', function() {
#!/usr/local/bin/node | |
// PBS 12/5/13 | |
// This is a BBEdit text filter for indenting (and beautifying) JavaScript. | |
// It goes in ~/Library/Application Support/BBEdit/Text Filters/ | |
// | |
// On my machine I assigned it a keyboard shortcut: cmd-' | |
// | |
// It requires the js-beautify Node module: https://github.com/einars/js-beautify | |
// |
<?php | |
add_action( 'wp_enqueue_scripts', 'enqueue_my_styles' ); | |
/** | |
* Example callback function that demonstrates how to properly enqueue conditional stylesheets in WordPress for IE. | |
* IE10 and up does not support conditional comments in standards mode. | |
* | |
* @uses wp_style_add_data() WordPress function to add the conditional data. | |
* @link https://developer.wordpress.org/reference/functions/wp_style_add_data/ |
<?php | |
/** | |
* DomTree | |
* | |
* Dump DomDocument based documents, suiting debugging needs | |
* | |
* @author hakre <http://hakre.wordpress.com/> | |
* @link http://stackoverflow.com/questions/26321597/getting-price-from-amazon-with-xpath/26323824#26323824 | |
* @link http://stackoverflow.com/questions/12108324/how-to-get-a-raw-from-a-domnodelist/12108732#12108732 | |
* @link http://stackoverflow.com/questions/684227/debug-a-domdocument-object-in-php/8631974#8631974 |