Pointing your domains to a gh-pages
branch requires three steps.
- Add the Github IPs as
A
records on Namecheap.
185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153
# Convert .flac to .mp3 (lossless) | |
for f in *.flac; do ffmpeg -i "$f" -aq 1 "${f%flac}mp3"; done | |
# Convert .flac to .mp3, compress to ~ 120k | |
for f in *.flac; do ffmpeg -i "$f" -aq 5 "${f%flac}mp3"; done | |
# Convert .flac to mp3, compress to ~ 128k | |
for f in *.flac; do ffmpeg -i "$f" -b:a 128k "${f%flac}mp3"; done | |
# Convert .flac to mp3, compress to variable 190k |
#!/bin/bash | |
# | |
# Script to setup a Elastic Beanstalk AMI with geospatial libraries and postGIS | |
# | |
# sh aws_ami_prep.sh > aws_ami_prep.log 2>&1 & | |
# Go to ec2-user home directory | |
cd /home/ec2-user | |
# yum libraries |
export HOMEBREW_INSTALL_BADGE='🍵' |
HTTP status code symbols for Rails | |
Thanks to Cody Fauser for this list of HTTP responce codes and their Ruby on Rails symbol mappings. | |
Status Code Symbol | |
1xx Informational | |
100 :continue | |
101 :switching_protocols | |
102 :processing |
# Apache .htaccess | |
# Thanks to Eric Duran http://ericduran.io/2013/05/31/angular-html5Mode-with-yeoman/ | |
# angularjs pushstate (history) support: | |
# See http://www.josscrowcroft.com/2012/code/htaccess-for-html5-history-pushstate-url-routing/ | |
<ifModule mod_rewrite.c> | |
RewriteEngine On | |
RewriteCond %{REQUEST_FILENAME} !-f | |
RewriteCond %{REQUEST_FILENAME} !-d |
function wp_api_encode_acf($data,$post,$context){ | |
$data['meta'] = array_merge($data['meta'],get_fields($post['ID'])); | |
return $data; | |
} | |
if( function_exists('get_fields') ){ | |
add_filter('json_prepare_post', 'wp_api_encode_acf', 10, 3); | |
} |
I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!
\
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.
THIS GIST WAS MOVED TO TERMSTANDARD/COLORS
REPOSITORY.
PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!