This gist assumes:
#Create bitbucket branch
##Create local branch
$ git checkout -b sync
Switched to a new branch 'sync'
$ git branch
master
* sync
| #!/bin/bash | |
| aptitude -y install expect | |
| // Not required in actual script | |
| MYSQL_ROOT_PASSWORD=abcd1234 | |
| SECURE_MYSQL=$(expect -c " | |
| set timeout 10 |
| // Add new image sizes | |
| function lc_insert_custom_image_sizes( $image_sizes ) { | |
| // get the custom image sizes | |
| global $_wp_additional_image_sizes; | |
| // if there are none, just return the built-in sizes | |
| if ( empty( $_wp_additional_image_sizes ) ) | |
| return $image_sizes; | |
| // add all the custom sizes to the built-in sizes | |
| foreach ( $_wp_additional_image_sizes as $id => $data ) { |
| #! /usr/bin/env bash | |
| ### | |
| # | |
| # install_mysql.sh | |
| # | |
| # This script assumes your Vagrantfile has been configured to map the root of | |
| # your application to /vagrant and that your web root is the "public" folder | |
| # (Laravel standard). Standard and error output is sent to | |
| # /vagrant/vm_build.log during provisioning. |
| /******************************************************************************* | |
| 1. DEPENDENCIES | |
| *******************************************************************************/ | |
| var gulp = require('gulp'); // gulp core | |
| sass = require('gulp-sass'), // sass compiler | |
| uglify = require('gulp-uglify'), // uglifies the js | |
| jshint = require('gulp-jshint'), // check if js is ok | |
| rename = require("gulp-rename"); // rename files | |
| concat = require('gulp-concat'), // concatinate js |
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
| /* | |
| Gulpfile.js file for the tutorial: | |
| Using Gulp, SASS and Browser-Sync for your front end web development - DESIGNfromWITHIN | |
| http://designfromwithin.com/blog/gulp-sass-browser-sync-front-end-dev | |
| Steps: | |
| 1. Install gulp globally: | |
| npm install --global gulp |
Custom recipe to get OS X 10.10 Yosemite running from scratch, setup applications and developer environment. I use this gist to keep track of the important software and steps required to have a functioning system after a semi-annual fresh install. On average, I reinstall each computer from scratch every 6 months, and I do not perform upgrades between distros.
This keeps the system performing at top speeds, clean of trojans, spyware, and ensures that I maintain good organizational practices for my content and backups. I highly recommend this.
You are encouraged to fork this and modify it to your heart's content to match your own needs.
