windyinsc windyinsc

Local SSL websites on macOS Sierra

These instructions will guide you through the process of setting up local, trusted websites on your own computer.

These instructions are intended to be used on macOS Sierra, but they have been known to work in El Capitan, Yosemite, Mavericks, and Mountain Lion.

NOTE: You may substitute the edit command for nano, vim, or whatever the editor of your choice is. Personally, I forward the edit command to Sublime Text:

alias edit="/Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl"

Shell scripts and one liners

Snippets, tips and tricks in no particular order. FOR ADVANCED USERS ONLY. Some of these one liners may be dangerous since they might delete files in loops. Please pay attention and make backups. :-)

Extracting a column from a text file

Extract the 10th column while skipping the first line:

awk -F ' ' 'NR!=1{print $10}' filename.txt

Install web development tools to Mavericks (OS X 10.9)

Strongly opinionated set of guides to quickly setup OS X Mavericks for web development. By default OS X hides stuff that normal people don't need to see. These settings are better defaults for developers.

I don't want: any sounds, annoying confirmation dialogs, hidden extensions, superflous animations, unnecessary things running like Dashboard, Notification center or Dock(Alfred/spotlight works better for me).

These are my opinions. Read this document through and pick up the good parts to your preferences.

System preferences

ANNOUNCEMENT

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!

\

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

	#!/bin/bash
	#####################################################
	# Name: Bash CheatSheet for Mac OSX
	#
	# A little overlook of the Bash basics
	#
	# Usage:
	#
	# Author: J. Le Coupanec
	# Date: 2014/11/04

	#!/bin/bash
	# Script to export Safari's reading list into a text file, then import this into Pocket or Evernote (or any service with a "email in content" feature).

	# First take all of Safari's Reading List items and place them in a text file.
	/usr/bin/plutil -convert xml1 -o - ~/Library/Safari/Bookmarks.plist \| grep -E -o '<string>http[s]{0,1}://.*</string>' \| grep -v icloud \| sed -E 's/<\/{0,1}string>//g' > readinglistlinksfromsafari.txt

	# Now loop over each of those URls within that text file and add them to pocket.
	while IFS= read -r line
	do
	echo $line

	# NPM CheatSheet.
	# Super easy intall: npm comes with node now.
	# To create your own npm package: https://www.npmjs.org/doc/misc/npm-developers.html
	# More: https://www.npmjs.org/doc/


	# 1. NPM Command Lines.
	# Local mode is the default.
	# Use --global or -g on any command to operate in global mode instead.

	# There was a day where I have too many color schemes in iTerm2 and I want to remove them all.
	# iTerm2 doesn't have "bulk remove" and it was literally painful to delete them one-by-one.

	# iTerm2 save it's preference in ~/Library/Preferences/com.googlecode.iterm2.plist in a binary format
	# What you need to do is basically copy that somewhere, convert to xml and remove color schemes in the xml files.

	$ cd /tmp/
	$ cp ~/Library/Preferences/com.googlecode.iterm2.plist .
	$ plutil -convert xml1 com.googlecode.iterm2.plist
	$ vi com.googlecode.iterm2.plist

	# ---------------------------------------------------------------------------
	#
	# Description: This file holds all my BASH configurations and aliases
	#
	# Sections:
	# 1. Environment Configuration
	# 2. Make Terminal Better (remapping defaults and adding functionality)
	# 3. File and Folder Management
	# 4. Searching
	# 5. Process Management