| db.getCollection('list').aggregate([ | |
| { | |
| $facet: { | |
| "events":[{ | |
| $match: { | |
| 'type': 'Event' | |
| } | |
| }], | |
| "tasks": [{ | |
| $match: { |
| angular.module('myApp', | |
| ['ngRoute', 'myApp.services', 'myApp.directives'] | |
| ) | |
| .config(function(AWSServiceProvider) { | |
| AWSServiceProvider.setArn('arn:aws:iam::<ACCOUNT_ID>:role/google-web-role'); | |
| }) | |
| .config(function(StripeServiceProvider) { | |
| StripeServiceProvider.setPublishableKey('pk_test_YOURKEY'); | |
| }) | |
| .config(function($routeProvider) { |
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);