Trying to deploy fabric recipes to an auto-scaling group on EC2 could prove pretty painful, except if you have this slick code snippet to define your server group in Fabric.
Basically I’m using boto to list all of the instances currently running in a specific security group, and then populate env.hosts.
This solves the problem for pushing to running hosts. In order to pull the latest codebase when a new instance fires up, we just stuck some scripts in /etc/rc.local – more on that later.
I needed a quick and simple script to monitor some of the API’s I manage. Since I already build in methods that fully test the webservice and backend database, I just had to wrap a single call and check the results from this method. Also I don’t want to rely on my servers being able to send mail, so I added support for AWS SES.
And the code…
I checked out DNSCrypt today, a new tool to help secure DNS resolution by encrypting the lookups from your machine to the DNS server.
The tool was developed by OpenDNS and is currently a preview release.
I just wanted to see the DNS traffic, so I performed a few lookups while capturing the packets…
Here is an example of a non-encrypted query:
And an encrypted query:
If you enable the lookups to traverse port 443, there will be tons of packets and I didn’t look at them.
One note worth mentioning – The client app creates a bunch of connections back to OpenDNS whenever you modify the settings.
This is some great technology and it is open-sourced. I’m assuming the networks who want total control of their users will just block the OpenDNS IP blocks to prevent users from encrypting their lookups.
You can fetch the source on GitHub – The entire Mac OS app is there!
Testing Octopress -> Feedburner -> Twitter
The rumors will finally be put to rest today at 1pm eastern.
I usually follow the Apple events at Engadget’s liveblog: http://www.engadget.com/2011/10/04/apples-lets-talk-iphone-keynote-liveblog/
Tornado uses the standard logging library, by default, and sends logs to STDOUT. Sometimes you may want logs stored in a database or flat-file.
This method is fairly simple. You could pass the ‘log_file_prefix’ parameter via the command-line, or more elegantly add the options in your code:
If you have multiple instances of the same app running, I would keep the logs separate by using the port number:
MongoLog is a really cool open-source centralized logging module for Python and MongoDB. It’s available on Github at https://github.com/andreisavu/mongodb-log.
Follow the installation docs in the README to get MongoLog all setup. After cloning and installing MongoLog, we need to modify our Tornado app.
First, import MongoLog:
Next we will override the ‘Application.log_request’ method to implement MongoLog.
After everything is up and running, you can view the raw logs in the database or use the web ui that ships with MongoLog:
Customized Galant from Ikea with lots of shiny Apple goodness.
An extra-wide touchpad and dual detachable iPad displays on a MacBook Pro. Wow! Add 32GB of RAM and quad SSD RAID too. I’m not sure why they left the optical drive in this mockup, that has got to go. Lets hope Apple is really brewing this, I will camp out on the street for this one!
