The answer is, FuelFrog. Over the past 9 weeks, we’ve conceived an idea, branded, implemented, tested, launched, and started to market a brand new web application. I’ll be talking more over the next few weeks about the technology behind FuelFrog and what’s coming up for new features!

We know that you care about how your car affects the environment. What better way to understand and manage this than to start tracking it! FuelFrog will help you keep an eye on your gas consumption, mileage, and also help you understand how gas prices affect your budget.
Through integration with Twitter, it’s easy to keep FuelFrog up to date. Each time you fill up, simply send @fuelfrog miles price gallons for example, my last fillup was @fuelfrog 320 3.539 10.293. We’ll do all the rest!
Log on to FuelFrog now and try it out!
Related posts
More in the “bigger isn’t always better” thread alluded to in my offsite backup post. Apparently, Amazon S3 was down for over 35 minutes.
Related posts
As any readers of the iContact blog may have learned, MogileFS has become an integral part of our infrastructure at iContact. Rather than store the bodies of messages in our database, we moved them to a quick&dirty storage method in our infrastructure long ago. This method was essentially a cheap WebDAV server and on each STORE command it would write to two backend servers and issue a GET from only one. About a month ago, we migrated most of our messages away from this older, less scalable method to our newer MogileFS backend.
Our MogileFS setup allows the disk space on each web server (normally unutilized) to form a cheap storage node, and make use of space that would otherwise go entirely unused.
On Monday 1/21 the database servers behind MogileFS paged with too many connections, which leads to Mogile going very slowly for a while, and sometimes requiring a restart of some of the nodes.
This database issue cascaded into us asking our Mogile client for item A, but receiving item B in response…
(more…)
Related posts
Recently I tried to use the Gallery Multiroot module/plugin to setup a new site based upon an existing Album in our gallery. Since we started sorting albums chronologically, we wanted to sort out the Dachshund photos separately. To do this, I used the Multiroot feature. Unfortunately, I couldn’t get this to work as I’m already using the Multisite plugin to host several Galleries off of my web server. The magic touch was to use the following file, the first line is key and had to be added to make things work in the Multisite configuration.
define('GALLERY_CONFIG_DIR', "/var/virtualwww/gallery.raschnet.com"); //I had to add this line
require('/usr/local/share/gallery2/embed.php');
$ret = GalleryEmbed::init(
array('embedUri' => '/',
'g2Uri' => 'http://gallery.raschnet.com/',
'apiVersion' => array(1, 2)
));
if ($ret) {
print '<body>' . $ret->getAsHtml() . '</body>';
return;
}
$gallery->setConfig('login', true);
$gallery->setConfig('defaultAlbumId', 28426);
$gallery->setConfig('breadcrumbRootId', 28426);
GalleryMain();
Now live: DRNA Gallery
Related posts