Ian Young ijy

Git Cheat Sheet

Initial Setup

Initialize a repo

Create an empty git repo or reinitialize an existing one

$ git init

Sometimes you need to keep two upstreams in sync with eachother. For example, you might need to both push to your testing environment and your GitHub repo at the same time. In order to do this simultaneously in one git command, here's a little trick to add multiple push URLs to a single remote.

Once you have a remote set up for one of your upstreams, run these commands with:

git remote set-url --add --push [remote] [original repo URL]
git remote set-url --add --push [remote] [second repo URL]

Once set up, git remote -v should show two (push) URLs and one (fetch) URL. Something like this:

Download portal for your OS.

Create a config file for portal

config.json

{
 "db-connection": "scribble:///tmp/portal",
 "log-level": "info",
 "server": true,

>> "just-proxy": true

#Installing ngrok on OSX

Download ngrok
Unzip it to your Applications directory
Create a symlink (instructions below)

Creating a symlink to ngrok

Run the following two commands in Terminal to create the symlink.

# cd into your local bin directory

Function	Shortcut
previous tab	⌘ + left arrow
next tab	⌘ + right arrow
go to tab	⌘ + number
go to window	⌘ + Option + Number
go to split pane by direction	⌘ + Option + arrow
go to split pane by order of use	⌘ + ] , ⌘ + [
split window horizontally (same profile)	⌘ + D
split window vertically (same profile)	⌘ + d

There are many types of caching that will improve website performance. Here are just five:

MySQL query caching

Every read query that Symphony executes is cached by MySQL. It is important to understand that this is not the result of the query, but the SQL statement itself. MySQL retains a pool of these statements so that they are quicker to execute in the future. This is pretty standard, and you can use it in your own applications too by using SELECT SQL_CACHE for your read queries.

Object caching

Once the database has been queried, the results are used to build objects (pages, data sources, sections, field, entries etc.). These objects are alive only for the lifespan of each page, and are destroyed at the end of each request. Systems such as Wordpress allow these objects to be cached and persisted between each page request (using APC, Memcache, flat files or MySQL), thereby shared between all users. Symphony doesn't do this, but it really should.

Fragment caching

If you have one piece of a p

	#!/bin/bash
	# Usage
	# $ ./install-cert-macos.sh "/path/to/cert"
	CERT_PATH="$1"

	# First, grab the SHA-1 from the provided SSL cert.
	CERT_SHA1=$(openssl x509 -in "$CERT_PATH" -sha1 -noout -fingerprint \| cut -d "=" -f2 \| sed "s/://g")

	# Next, grab the SHA-1s of any standard.dev certs in the keychain.
	# Don't return an error code if nothing is found.

	# * * * * * command to execute
	# ┬ ┬ ┬ ┬ ┬
	# │ │ │ │ │
	# │ │ │ │ │
	# │ │ │ │ └───── day of week (0 - 6) (0 to 6 are Sunday to Saturday, or use names)
	# │ │ │ └────────── month (1 - 12)
	# │ │ └─────────────── day of month (1 - 31)
	# │ └──────────────────── hour (0 - 23)
	# └───────────────────────── min (0 - 59)

	/*
	* Nunjucks + Express
	* I couldn't find anything that helped me setup the enviornment
	* correctly for these in the latest vesion of Express 4 (at the time
	* of writing this).
	*
	* This Gist for those that want to keep using Nunjucks with Express 4.
	* This also goes over working with a Nunjucks environment to use custom
	* filters, extensions, etc.
	*

	#!/bin/bash

	libs=( "/usr/local/lib/libmacfuse_i32.2.dylib" \
	"/usr/local/lib/libosxfuse_i32.2.dylib" \
	"/usr/local/lib/libosxfuse_i64.2.dylib" \
	"/usr/local/lib/libmacfuse_i64.2.dylib" \
	"/usr/local/lib/libosxfuse_i32.la" \
	"/usr/local/lib/libosxfuse_i64.la" \
	"/usr/local/lib/pkgconfig/osxfuse.pc" )