<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>need:brain &#187; django</title>
	<atom:link href="http://www.needbrain.de/tag/django/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.needbrain.de</link>
	<description>The knowledge community of ATW</description>
	<lastBuildDate>Tue, 07 Apr 2015 22:35:24 +0000</lastBuildDate>
	<language>de-DE</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9-RC2</generator>
	<item>
		<title>Using django-tables2, django-filters and django-crispy-forms together</title>
		<link>http://www.needbrain.de/2014/05/using-django-tables2-django-filters-and-django-crispy-forms-together/</link>
		<comments>http://www.needbrain.de/2014/05/using-django-tables2-django-filters-and-django-crispy-forms-together/#comments</comments>
		<pubDate>Wed, 07 May 2014 19:07:04 +0000</pubDate>
		<dc:creator><![CDATA[andy]]></dc:creator>
				<category><![CDATA[Resources]]></category>
		<category><![CDATA[brain]]></category>
		<category><![CDATA[django]]></category>

		<guid isPermaLink="false">http://www.needbrain.de/?p=293</guid>
		<description><![CDATA[I was recently working on a very CRUDy prototype and decided to use some Django applications and tools together I hadn&#8217;t combined before: A view that uses all three apps together could look like this: class FooTableView(TemplateView): template_name = &#8216;myapp/foo_list. http://kuttler.eu/post/using-django-tables2-filters-crispy-forms-together/]]></description>
		<wfw:commentRss>http://www.needbrain.de/2014/05/using-django-tables2-django-filters-and-django-crispy-forms-together/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Scaling Your Write-Heavy Django App: A Case Study</title>
		<link>http://www.needbrain.de/2014/01/scaling-your-write-heavy-django-app-a-case-study/</link>
		<comments>http://www.needbrain.de/2014/01/scaling-your-write-heavy-django-app-a-case-study/#comments</comments>
		<pubDate>Mon, 13 Jan 2014 08:44:07 +0000</pubDate>
		<dc:creator><![CDATA[andy]]></dc:creator>
				<category><![CDATA[Resources]]></category>
		<category><![CDATA[brain]]></category>
		<category><![CDATA[dev]]></category>
		<category><![CDATA[django]]></category>
		<category><![CDATA[scale]]></category>

		<guid isPermaLink="false">http://www.needbrain.de/?p=119</guid>
		<description><![CDATA[Content management systems and other read-heavy Django apps are relatively easy to scale. You add some caching, and maybe a couple extra web servers for good measure. Scaling write-heavy apps is another matter, both from an app server and a database server perspective. http://lanyrd.com/2013/djangocon/scmqwy/]]></description>
		<wfw:commentRss>http://www.needbrain.de/2014/01/scaling-your-write-heavy-django-app-a-case-study/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
