Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
tree: bf25f50715
Fetching contributors…

Cannot retrieve contributors at this time

172 lines (134 sloc) 9.066 kb
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>JustCramer</title>
<link href="http://justcramer.com/atom.xml" rel="self"/>
<updated>2012-08-30T23:15:12-07:00</updated>
<id>http://justcramer.com/</id>
<entry>
<title>Moving Sentry from Heroku to Hardware</title>
<link href="http://justcramer.com/2012/08/30/how-noops-works-for-sentry"/>
<updated>2012-08-30T20:59:00-07:00</updated>
<id>http://justcramer.com/2012/08/30/how-noops-works-for-sentry</id>
<content type="html">Update: Don&amp;#8217;t decide against Heroku just because you&amp;#8217;ve read my blog. It makes some things (especially
prototyping) very easy, and with certain kinds of applications it can work very well.
I&amp;#8217;ve talked a lot about how I run getsentry.com, mostly with my experiences
on Heroku and &amp;hellip;</content>
<author>
<name>David Cramer</name>
<url>http://justcramer.com/</url>
</author>
</entry>
<entry>
<title>Scaling Your Clouds</title>
<link href="http://justcramer.com/2012/06/03/scaling-your-clouds"/>
<updated>2012-06-03T17:53:00-07:00</updated>
<id>http://justcramer.com/2012/06/03/scaling-your-clouds</id>
<content type="html">My post yesterday seems to have gotten all the cloud fanboy&amp;#8217;s panties into a twist, so I figured I&amp;#8217;d give them something
else to rage about.
There were lots of claims that without the cloud you can&amp;#8217;t scale, or you dont have redundancy, or you can&amp;#8217;t come up
with the result &amp;hellip;</content>
<author>
<name>David Cramer</name>
<url>http://justcramer.com/</url>
</author>
</entry>
<entry>
<title>The Cloud is Not For You</title>
<link href="http://justcramer.com/2012/06/02/the-cloud-is-not-for-you"/>
<updated>2012-06-02T13:57:00-07:00</updated>
<id>http://justcramer.com/2012/06/02/the-cloud-is-not-for-you</id>
<content type="html">Update: Did I hurt your feelings with this post? Read
Scaling your Clouds so you can rage even more.
Well, maybe not specifically you, but the mass that screams it will solve their problems.
It&amp;#8217;s been a fun year so far. There&amp;#8217;s been exciting things happening both for me personally, as &amp;hellip;</content>
<author>
<name>David Cramer</name>
<url>http://justcramer.com/</url>
</author>
</entry>
<entry>
<title>Distributing Work in Python Without Celery</title>
<link href="http://justcramer.com/2012/05/04/distributing-work-without-celery"/>
<updated>2012-05-04T15:12:00-07:00</updated>
<id>http://justcramer.com/2012/05/04/distributing-work-without-celery</id>
<content type="html">We&amp;#8217;ve been migrating a lot of data to various places lately at DISQUS. These generally have been things like running
consistancy checks on our PostgreSQL shards, or creating a new system which requires a certain form of denormalized data. It
usually involves iterating through the results of &amp;hellip;</content>
<author>
<name>David Cramer</name>
<url>http://justcramer.com/</url>
</author>
</entry>
<entry>
<title>Using Travis-CI with Python and Django</title>
<link href="http://justcramer.com/2012/05/03/using-travis-ci"/>
<updated>2012-05-03T11:13:00-07:00</updated>
<id>http://justcramer.com/2012/05/03/using-travis-ci</id>
<content type="html">I&amp;#8217;ve been using Travis-CI for a while now. Both my personal projects,
and even several of the libraries we maintain at DISQUS rely on it for Continuous Integration. I figured it was about time to confess
my undenying love for Travis, and throw up some notes about the defaults we use in our &amp;hellip;</content>
<author>
<name>David Cramer</name>
<url>http://justcramer.com/</url>
</author>
</entry>
<entry>
<title>Sticking With Standards</title>
<link href="http://justcramer.com/2012/04/24/sticking-with-standards"/>
<updated>2012-04-24T22:23:00-07:00</updated>
<id>http://justcramer.com/2012/04/24/sticking-with-standards</id>
<content type="html">More and more I&amp;#8217;m seeing the &amp;#8220;requirements.txt pattern&amp;#8221; come up. This generally refers to projects (but not just), and
seems to have started around the same time as Heroku adopting Python. I feel like this is something that matters in the
Python world, and because I have an &amp;hellip;</content>
<author>
<name>David Cramer</name>
<url>http://justcramer.com/</url>
</author>
</entry>
<entry>
<title>Using Arrays as Materialized Paths in Postgres</title>
<link href="http://justcramer.com/2012/04/08/using-arrays-as-materialized-paths-in-postgres"/>
<updated>2012-04-08T16:52:00-07:00</updated>
<id>http://justcramer.com/2012/04/08/using-arrays-as-materialized-paths-in-postgres</id>
<content type="html">Something we&amp;#8217;ve been casually working on at Disqus for quite some time is an improved pagination method for threaded comments. This is obviously pretty important to us, it drives the very foundation of our product. It also happens to be an area that&amp;#8217;s somewhat challenging, and has a &amp;hellip;</content>
<author>
<name>David Cramer</name>
<url>http://justcramer.com/</url>
</author>
</entry>
<entry>
<title>Scaling Schema Changes</title>
<link href="http://justcramer.com/2011/11/10/scaling-schema-changes"/>
<updated>2011-11-10T16:06:00-08:00</updated>
<id>http://justcramer.com/2011/11/10/scaling-schema-changes</id>
<content type="html">I frequently get asked how Disqus deals with schema changes. It&amp;#8217;s a fair question, since we operate a fairly large amount of servers, but I also tend to think the answer is somewhat obvious. So let&amp;#8217;s start with the problem of schema changes at scale (in PostgreSQL).
Generally you have &amp;hellip;</content>
<author>
<name>David Cramer</name>
<url>http://justcramer.com/</url>
</author>
</entry>
<entry>
<title>Integrating Django with Nose at DISQUS</title>
<link href="http://justcramer.com/2011/08/05/extending-django-nose"/>
<updated>2011-08-05T00:00:00-07:00</updated>
<id>http://justcramer.com/2011/08/05/extending-django-nose</id>
<content type="html">About a month ago we decided to make the transition off of Django&amp;#8217;s test suite over to the Nose runners. Our main selling point was the extensibility, and the existing ecosystem of plugins. Four weeks later I&amp;#8217;m happy to say we&amp;#8217;re running (basically) Nose with some minor extensions &amp;hellip;</content>
<author>
<name>David Cramer</name>
<url>http://justcramer.com/</url>
</author>
</entry>
<entry>
<title>Python and OS X Lion</title>
<link href="http://justcramer.com/2011/07/20/python-and-os-x-lion"/>
<updated>2011-07-20T00:00:00-07:00</updated>
<id>http://justcramer.com/2011/07/20/python-and-os-x-lion</id>
<content type="html">Just a few quick tips that I&amp;#8217;ve had to run through and discover today while upgrading to Lion.
Start by installing Xcode 4, which is available via the App Store (for free now). This will fix your missing distutils package (which probably fixes a majority of your issues). You&amp;#8217;ll also &amp;hellip;</content>
<author>
<name>David Cramer</name>
<url>http://justcramer.com/</url>
</author>
</entry>
</feed>
Jump to Line
Something went wrong with that request. Please try again.