rydurham

# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
[ -z "$PS1" ] && return

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

rydurham

# Some useful Aliases
alias cls=clear
alias composer='/usr/local/bin/composer.phar'


# Add Git Branch Info
parse_git_branch() {
  git branch 2> /dev/null | sed -e '/^[^*]/d' -e 's/* \(.*\)/(\1)/'
}

rydurham

sudo apt-get install phpmyadmin

sudo vim /etc/apache2/apache2.conf

Include /etc/phpmyadmin/apache.conf

sudo service apache2 restart

rydurham

### Keybase proof

I hereby claim:

  * I am rydurham on github.
  * I am rydurham (https://keybase.io/rydurham) on keybase.
  * I have a public key whose fingerprint is 0A67 6818 87ED 7D1D 26A8  CEED 0279 B429 EC4F 1C27

To claim this, I am signing this object:

rydurham

Via http://christoph-rumpel.com/2014/02/how-to-laravel-series-lets-talk-gulp/


$ node -v
v0.10.28

$ npm -v
1.4.24

rydurham

$breakpoints: (
        'small' ( '( max-width:  616px )'),
        'medium' ( '( min-width:  617px ) and (max-width: 1066px)'),
        'large'  ( '( min-width: 1067px )')
);

@mixin respond-to($name, $push: false) {
  // If the key exists in the map
  @if map-has-key($breakpoints, $name) {
    // Prints a media query based on the value

rydurham

<?php

return array(

	'EMAIL_HOST' => '',

	'EMAIL_PORT' => 587,

	'EMAIL_USERNAME' => '',

rydurham

http://teleogistic.net/2011/05/revisiting-git-github-and-the-wordpress-org-plugin-repository


So, for the last six months or so, I’ve used a modified version of the release workflow described in Part Three. First, I have a local branch, which I call svn, which tracks trunk:

  git checkout -b svn trunk

At release time, I check out the svn branch, and do a squash merge. This means that all changes since the last commit to the svn branch are laid on top of svn as if they were a single set of changes. You can then commit these changes as a single changeset (thus keepin’ it linear, and keepin’ it short for Otto’s sake):

  git checkout svn # if you're not already on it

rydurham

#!/bin/bash -e
clear
echo "============================================"
echo "WordPress Install Script"
echo "============================================"
echo "Database Name: "
read -e dbname
echo "Database User: "
read -e dbuser
echo "Database Password: "

rydurham

{
  "name": "project-name",
  "version": "1.0.0",
  "description": "description",
  "repository": {
    "type": "git",
    "url": ""
  },
  "author": "Ryan C. Durham",
  "devDependencies": {