| alias nom='npm cache clean && rm -rf node_modules && mkdir node_modules && touch node_modules/.metadata_never_index && npm install' | |
| alias bom='bower cache clean && rm -rf bower_components && mkdir bower_components && touch bower_components/.metadata_never_index && bower install' |
| // Show a list of previous commits | |
| git log | |
| git log --oneline --since=1.days | |
| git log --no-merges | |
| git log --since=1.days | |
| git log --pretty=format:"%s" --no-merges -n 25 | |
| git log --pretty=format:"%s" --no-merges --since=1.days | |
| git log --pretty=format:"%s" --no-merges --since=18.hours |
Steps to setup a new OS X laptop with a data science & computational biology development environment.
Last updated: 7 Jan 2017 macOS: Yosemite => Sierra
Sure you could try to do this from dotfiles, but historically something has broken and required manual input anyway. So, inspired by the pragmatism of paul irish bash setup script and a few other gists written in markdown like this, I rolled my own.
Homebrew is a package management system for OS X. You can read more about it here, or simply run
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"to install it.
| <?php | |
| /** | |
| * Add the metabox. | |
| */ | |
| function my_url_add_metabox() { | |
| add_meta_box( | |
| 'my_url_section', // The HTML id attribute for the metabox section | |
| 'My URL Metabox Title', // The title of your metabox section |
_________ _____ _______________ _____
\_ ___ \\ \\___________ \____ / ____\ ~/.bash/cliref.md
/ \ \/| | | || _/ __ \ __\ copy/paste from whatisdb
\ \___|__ |_|_ || | \ __/|_ | http://pastebin.com/yGmGiDQX
\________ /_____ \_||____|_ /____ /_| [email protected]
20160515 \/ 1527 \/ \/ \/
alias CLIRef.txt='curl -s "http://pastebin.com/raw/yGmGiDQX" | less -i'
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.
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
| #XLarge DBInstanceClassMemory = 15892177440 = 14.8GB | |
| #/32 = 496630545 = 473MB | |
| #/64 = 248315272 = 236MB | |
| #/128 = 124157636 = 118MB | |
| #/256 = 62078818 = 59MB | |
| #/512 = 31039409 = 29MB | |
| #/12582880 = 1263 #default same divisor as max_connections = 4041.6MB = 4237924762 | |
| #/25165760 = 623 # half of max_connections = 1993.6MB | |
| #/50331520 = 315 # quarter of max_connections = 1008MB = 1056964608 | |
| #*(3/4) #default innodb pool size = 11922309120 |
##Auto-deploy with php and github on an Ubuntu Amazon EC2 box
Fork from other gist Build auto-deploy with php and git(hub) on an EC2 AMAZON AMI instance - Covers a basic Ubuntu isntall
When ever it says www-data below, it's the user Apache runs under. So if your apache user is called something else, change it to that.
##Install git
sudo aptitude install git-core
| #!/bin/sh | |
| ### | |
| # SOME COMMANDS WILL NOT WORK ON macOS (Sierra or newer) | |
| # For Sierra or newer, see https://github.com/mathiasbynens/dotfiles/blob/master/.macos | |
| ### | |
| # Alot of these configs have been taken from the various places | |
| # on the web, most from here | |
| # https://github.com/mathiasbynens/dotfiles/blob/5b3c8418ed42d93af2e647dc9d122f25cc034871/.osx |