Pirated from a long forgotten place...apologies to the respective copyright holders. Just paste this in your .bashrc for git-aware goodness:
Pirated from a long forgotten place...apologies to the respective copyright holders. Just paste this in your .bashrc for git-aware goodness:
The AWS Elastic Load Balancing FAQ has this very relevant question:
Can I configure my Amazon EC2 instances to only accept traffic from the Elastic Load Balancer?
followed by an ever so helpful response:
Yes.
Seriously - no links, no reference to documentation, nothing. With such a tremendous investment in infrastructure you'd think Amazon might spend a day or two on documentation...alas.
Insult to injury it's also not at all obvious what you need to do to configure your Security Group to support this very commonly desired configuration. I'm here to help.
Use the not-so-documented 'amazon-elb/amazon-elb-sg' Security Group name as the Inbound Source for your Security Group rule to filter on traffic coming from your AWS ELB. Enjoy!
During today's maintenance run of git-gc on our Mac hosted repo I encountered screenfulls of nasty fatal error messages - but the last two were a clue to the root cause:
fatal: Unable to create temporary file: Too many open files
error: failed to run repack
This related post helped me find a quick cure which involved simply bumping the ulimit up temporarily.
# ulimit -n 10024
> git gc
Easy fix for a potentially bad day.
Steps I took to get a Play framework app up and running on a micro AWS instance running Ubuntu 11.10
There are three possible gotchas with FunctionalTest on Play Framework 1.2.4: