| { | |
| "$schema": "https://raw.githubusercontent.com/jsonresume/resume-schema/v1.0.0/schema.json", | |
| "basics": { | |
| "name": "Matthew Hollings", | |
| "label": "Programmer", | |
| "image": "", | |
| "email": "", | |
| "phone": "(912) 555-4321", | |
| "url": "http://richardhendricks.example.com", | |
| "summary": "Richard hails from Tulsa. He has earned degrees from the University of Oklahoma and Stanford. (Go Sooners and Cardinal!) Before starting Pied Piper, he worked for Hooli as a part time software developer. While his work focuses on applied information theory, mostly optimizing lossless compression schema of both the length-limited and adaptive variants, his non-work interests range widely, everything from quantum computing to chaos theory. He could tell you about it, but THAT would NOT be a “length-limited” conversation!", |
| ## The Problem | |
| Standard practices say no non-root process gets to talk to the Internet on a port less than 1024. How, then, could I get Node talking on port 80 on EC2? (I wanted it to go as fast as possible and use the smallest possible share of my teeny tiny little micro-instance's resources, so proxying through nginx or Apache seemed suboptimal.) | |
| ## The temptingly easy but ultimately wrong solution: | |
| Alter the port the script talks to from 8000 to 80: | |
| }).listen(80); |
| #!/usr/bin/env sh | |
| ## | |
| # This is script with usefull tips taken from: | |
| # https://github.com/mathiasbynens/dotfiles/blob/master/.osx | |
| # | |
| # install it: | |
| # curl -sL https://raw.github.com/gist/2108403/hack.sh | sh | |
| # |
| http://toroid.org/ams/git-website-howto | |
| SET UP BARE REMOTE | |
| 1. set up local repo | |
| 2. on remote mkdir eg repos/website.git | |
| 3. in website.git - git init --bare | |
| 4. mkdir to be served from eg sites/website.co.uk | |
| 5. in website.git edit hooks/post-receive | |
| #!/bin/sh | |
| GIT_WORK_TREE=/sites/website.co.uk git checkout -f |
| // http://paulirish.com/2011/requestanimationframe-for-smart-animating/ | |
| // http://my.opera.com/emoller/blog/2011/12/20/requestanimationframe-for-smart-er-animating | |
| // requestAnimationFrame polyfill by Erik Möller | |
| // fixes from Paul Irish and Tino Zijdel | |
| (function() { | |
| var lastTime = 0; | |
| var vendors = ['ms', 'moz', 'webkit', 'o']; | |
| for(var x = 0; x < vendors.length && !window.requestAnimationFrame; ++x) { |
| void setup() { | |
| size(400, 300); | |
| background(255); | |
| } | |
| void touchMove(TouchEvent touchEvent) { | |
| // empty the canvas | |
| noStroke(); | |
| fill(255); | |
| rect(0, 0, 400, 300); |
(a gist based on the old toolmantim article on setting up remote repos)
To collaborate in a distributed development process you’ll need to push code to remotely accessible repositories.
This is somewhat of a follow-up to the previous article setting up a new rails app with git.
Set up the new bare repo on the server:
