SSH into your EC2 instance. Run the following:
$ sudo yum install gcc This may return an "already installed" message. That's OK.
$ wget http://download.redis.io/redis-stable.tar.gz && tar xvzf redis-stable.tar.gz && cd redis-stable && make
SSH into your EC2 instance. Run the following:
$ sudo yum install gcc This may return an "already installed" message. That's OK.
$ wget http://download.redis.io/redis-stable.tar.gz && tar xvzf redis-stable.tar.gz && cd redis-stable && make
| class @BaseCtrl | |
| @register: (app, name) -> | |
| name ?= @name || @toString().match(/function\s*(.*?)\(/)?[1] | |
| app.controller name, this | |
| @inject: (annotations...) -> | |
| ANNOTATION_REG = /^(\S+)(\s+as\s+(\w+))?$/ | |
| @annotations = _.map annotations, (annotation) -> |
| <!doctype html> | |
| <html ng-app="Demo" ng-controller="DemoController"> | |
| <head> | |
| <meta charset="utf-8" /> | |
| <title> | |
| Forced Repaints In Directive Can Cause Accidental Scrolling In AngularJS | |
| </title> | |
| </head> | |
| <body> |
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.)
Alter the port the script talks to from 8000 to 80:
}).listen(80);