- How one developer just broke Node, Babel and thousands of projects in 11 lines of JavaScript – Link
- The npm Blog – kik, left-pad, and npm – Link
- Electron – Build cross platform desktop apps with web technologies – Link
- What every Browser knows about you – Link
- Android Studio 2.0 | Android Developers Blog – Link
- Dev Centers – Directory of developer center websites with memorable URL shortcuts – Link
- Java Forever And Ever Movie (Java vs Windows .Net) – Link
- Everything announced at Facebook's F8 conference – Link
- New Facebook dev tools include Account Kit, push and quote sharin
This outline for building and installing Git has only been tested against Mac OS X 10.7.x (Lion). While these steps may work for previous versions of Mac OS X, I cannot confirm this. Furthermore, you're on your own, if you screw something up, it's not my fault.
Xcode 4 includes the Git binary at the application level so it's available to itself (located at /Applications/Xcode.app/Contents/Developer/usr/bin/git
). Additionally, Xcode 4 includes a new "Downloads" preference pane to install optional components, one of which are the Command Line Tools (similar to the Dev Tools package that shipped with older versions of Xcode) and once installed, Git (and many other utilities, such as make
) is installed at the system level (located at /usr/bin
).
*Note: You don't have to install Xcode to use the Command Line Tools; it can be downloaded independently from the Apple Developer site (you need to login, but it's free
#!/bin/bash | |
# check if stdout is a terminal | |
if [ -t 1 ]; then | |
# see if it supports colors | |
ncolors=$(tput colors) | |
if [[ -n "$ncolors" && $ncolors -ge 8 ]]; then | |
bold="$(tput bold)" | |
underline="$(tput smul)" |
$ npm install -g http-server
$ http-server -p 8000 -a foo.bar.com
Would serve PWD at http://foo.bar.com/
[ | |
{ | |
"homepage": "http://digitaljhelms.github.com", | |
"name": "digitaljhelms", | |
"description": "finally blogging...", | |
"author": "Jeremy Helms", | |
"post": { | |
"url": "http://digitaljhelms.github.com/howto/creating-a-branch-with-no-parents-or-history", | |
"slug": "creating-a-branch-with-no-parents-or-history", | |
"title": "Create a Git Branch without Parents or History", |
#!/bin/bash | |
while IFS= read -r LINE || [ "$LINE" ]; do | |
# https://curl.haxx.se/docs/manpage.html | |
IN=$(curl -o /dev/null --silent --head --write-out "%{http_code};%{redirect_url}" "$LINE") | |
# https://stackoverflow.com/a/5257398 | |
arrIN=(${IN//;/ }) | |
if [ "${arrIN[0]}" = "301" ] || [ "${arrIN[0]}" = "302" ]; then |
#!/bin/bash | |
AUTH_EMAIL='your@email' # dnsimple account email address | |
AUTH_TOKEN='your-api-token' # dnsimple api token | |
DOMAIN_ID='yourdomain.com' # domain name or id | |
RECORD_ID='12345' # record id to update | |
IP="`curl http://icanhazip.com/`" | |
curl -H "X-DNSimple-Token: $AUTH_EMAIL:$AUTH_TOKEN" \ | |
-H "Accept: application/json" \ |
Using a symlink to easily view the AEM log on macOS +10.12 in the Console application (without having to manually find/open the log file) won’t work anymore, it requires a hard link:
brew install hardlink-osx
mkdir ~/Library/Logs/AEM
hln <PROJECT ROOT>/AEM/author/crx-quickstart/logs/error.log ~/Library/Logs/AEM/<PROJECT NAME>.error.log
open -a Console.app
Anytime you want to view the log, it’s at Reports → ~/Library/Logs → AEM → .error.log
I hereby claim:
- I am digitaljhelms on github.
- I am digitaljhelms (https://keybase.io/digitaljhelms) on keybase.
- I have a public key whose fingerprint is F930 EA2C 5B7B FB40 CE37 5C87 998D 75C9 EE6C 2676
To claim this, I am signing this object:
# bash alias | |
alias subl='/Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl' | |
# bash function, usage: $ st -p [projectname] -opt2 -opt3 | |
function st() { | |
if [ -n "$1" -a -n "$2" ]; then # if more than one argument | |
if [ "$1" = "-p" -o "$1" = "--project" ]; then # if arg1 is -p or --project | |
local projectfile="$2" | |
[[ $projectfile != *.sublime-project ]] && projectfile="$2.sublime-project" # detect if arg2 already includes the ext | |
if [ -e $projectfile ]; then # does project file exist? |