wilmoore

<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
    xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:ext="http://www.liquibase.org/xml/ns/dbchangelog-ext"
    xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-2.0.xsd
    http://www.liquibase.org/xml/ns/dbchangelog-ext http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-ext.xsd">

</databaseChangeLog>

wilmoore

Building Docker image with Packer and provisioning with Ansible

Overview

Packer

• Packer is used to build image from a base image, perform provisions and store (commit) the final image.

• We use provisioners and Packer templates to do the actual work to create the final image.

• We use Ansible for provisioning.

wilmoore

<?php

/**
 * SplClassLoader implementation that implements the technical interoperability
 * standards for PHP 5.3 namespaces and class names.
 *
 * http://groups.google.com/group/php-standards/web/final-proposal
 *
 *     // Example which loads classes for the Doctrine Common package in the
 *     // Doctrine\Common namespace.

wilmoore

// Scraping Made Easy with jQuery and SelectorGadget 
// (http://blog.dtrejo.com/scraping-made-easy-with-jquery-and-selectorga)
// by David Trejo
// 
// Install node.js and npm:
//    http://joyeur.com/2010/12/10/installing-node-and-npm/
// Then run
//    npm install jsdom jquery http-agent
//    node numresults.js
// 

wilmoore

Sass/Less Comparison

In this document I am using Sass's SCSS syntax. You can choose to use the indented syntax in sass, if you prefer it, it has no functional differences from the SCSS syntax.

For less, I'm using the ruby version because this is what they suggest on the website. The javascript version may be different.

Variables

wilmoore

How to free Symfony2 from the sandbox tutorial (with some help from Git)
http://symfony2tips.blogspot.com/2011/02/how-to-free-symfony2-from-sandbox.html

wilmoore

Grab latest ubuntu 10.10 64bit canonical ami from alestic - http://alestic.com/
Create new ec2 instance + add ebs volume (/dev/sdf) + elastic ip


# update hostname + /etc/host

sudo hostname fe1-us.dustinwhittle.net


# add user account + configure keys in sshd_config + add ssh key

wilmoore

defprotocol Dict.Protocol do
  def keys(dict)
  def values(dict)
  def size(dict)
  def has_key?(dict, key)
  def get(dict, key, default)
  def get!(dict, key)
  def put(dict, key, val)
  def put_new(dict, key, val)
  def delete(dict, key)

wilmoore

#
# This is the way I configured my ruby environment on ArchLinux.
# 
# I don't like the overhead of rvm, so I use chruby to switch between ruby versions.
# So first you need to install chruby from source: 
# 
# https://github.com/postmodern/chruby#install
#
# To build ruby from source I use ruby-build, so after chruby we install ruby-build:
#

wilmoore

Avoid jQuery When Possible

jQuery does good jobs when you're dealing with browser compatibility. But we're living in an age that fewer and fewer people use old-school browsers such as IE <= 7. With the growing of DOM APIs in modern browsers (including IE 8), most functions that jQuery provides are built-in natively.

When targeting only modern browsers, it is better to avoid using jQuery's backward-compatible features. Instead, use the native DOM API, which will make your web page run much faster than you might think (native C / C++ implementaion v.s. JavaScript).

If you're making a web page for iOS (e.g. UIWebView), you should use native DOM APIs because mobile Safari is not that old-school web browser; it supports lots of native DOM APIs.

If you're making a Chrome Extension, you should always use native APIs, not only because Chrome has almost the latest DOM APIs available, but this can also avoid performance issue and unnecessary memory occupation (each jQuery-driven extension needs a separate