<?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"
	>

<channel>
	<title>sine qua non</title>
	<atom:link href="http://blog.sinequanon.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sinequanon.net</link>
	<description></description>
	<pubDate>Mon, 03 Nov 2008 21:23:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
	<language>en</language>
			<item>
		<title>Arica, Chile</title>
		<link>http://blog.sinequanon.net/2008/11/arica-chile/</link>
		<comments>http://blog.sinequanon.net/2008/11/arica-chile/#comments</comments>
		<pubDate>Mon, 03 Nov 2008 21:23:51 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[meta]]></category>

		<category><![CDATA[arica]]></category>

		<category><![CDATA[chile]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=119</guid>
		<description><![CDATA[Things slowed down on the blog while I&#8217;ve been in Arica, Chile providing data support for the VOCALS project. I&#8217;ve gotten a few pictures online with hopefully more to follow soon. I brought my bike, that&#8217;s been good. There&#8217;s a few decent beers, some excellent wine, and top-notch seafood everywhere. I&#8217;m trying to get to [...]]]></description>
		<wfw:commentRss>http://blog.sinequanon.net/2008/11/arica-chile/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Rails logged_in_user idiom</title>
		<link>http://blog.sinequanon.net/2008/10/rails-logged_in_user-idiom/</link>
		<comments>http://blog.sinequanon.net/2008/10/rails-logged_in_user-idiom/#comments</comments>
		<pubDate>Tue, 07 Oct 2008 18:04:21 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[rails]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=113</guid>
		<description><![CDATA[I recently refactored another developer&#8217;s code to clean up some massive amounts of database pings to retrieve the current user object. The main problem was in the use of the logged_in_user or current_user idiom in Rails. Several places give good examples but leave out the details that were bugging my project.

user.id
Firstly, don&#8217;t store the user [...]]]></description>
		<wfw:commentRss>http://blog.sinequanon.net/2008/10/rails-logged_in_user-idiom/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Fall colors</title>
		<link>http://blog.sinequanon.net/2008/10/fall-colors/</link>
		<comments>http://blog.sinequanon.net/2008/10/fall-colors/#comments</comments>
		<pubDate>Thu, 02 Oct 2008 20:05:53 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[bikes]]></category>

		<category><![CDATA[flyfishing]]></category>

		<category><![CDATA[aspen]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=108</guid>
		<description><![CDATA[It&#8217;s been a great couple of weeks to be out and about aspen-peeping (what am I doing sitting here?). Had some good bike rides and fishing amongst the fall colors. Seems to be a bit more orange and red amongst the golden aspens this year. Here&#8217;s a couple pix. A few more in my plog.


]]></description>
		<wfw:commentRss>http://blog.sinequanon.net/2008/10/fall-colors/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Grails error.gsp security</title>
		<link>http://blog.sinequanon.net/2008/10/grails-errorgsp-security/</link>
		<comments>http://blog.sinequanon.net/2008/10/grails-errorgsp-security/#comments</comments>
		<pubDate>Wed, 01 Oct 2008 20:13:59 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[grails]]></category>

		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=91</guid>
		<description><![CDATA[The default generated error.gsp view in Grails displays the stacktrace for any exceptions that occur. That&#8217;s nice for debugging in a development environment but it is a security issue for production as it is information leakage. We can easily turn this off when not in development, and do something useful like redirect to the application [...]]]></description>
		<wfw:commentRss>http://blog.sinequanon.net/2008/10/grails-errorgsp-security/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Grails stacktrace.log</title>
		<link>http://blog.sinequanon.net/2008/09/grails-stacktracelog/</link>
		<comments>http://blog.sinequanon.net/2008/09/grails-stacktracelog/#comments</comments>
		<pubDate>Tue, 30 Sep 2008 23:58:57 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[grails]]></category>

		<category><![CDATA[logging]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=78</guid>
		<description><![CDATA[Grails 1.0.x started creating a stacktrace.log file in the directory where the servlet container starts. In a development environment, using grails run-app, that&#8217;s simple enough&#8212; it appears in the top level of your application. In a production environment, this becomes a problem. Your production container (e.g. Tomcat) may start someplace where it can&#8217;t create files, [...]]]></description>
		<wfw:commentRss>http://blog.sinequanon.net/2008/09/grails-stacktracelog/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Grails logging</title>
		<link>http://blog.sinequanon.net/2008/09/grails-logging/</link>
		<comments>http://blog.sinequanon.net/2008/09/grails-logging/#comments</comments>
		<pubDate>Wed, 24 Sep 2008 19:39:07 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[grails]]></category>

		<category><![CDATA[logging]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=72</guid>
		<description><![CDATA[To turn on display of debug log messages in Grails 1.0.2, add this to the bottom of grails-app/conf/Config.groovy:


environments {
  development {
    log4j {
      logger {
         grails."app"="debug,stdout"
      }
    }
  }
}


With [...]]]></description>
		<wfw:commentRss>http://blog.sinequanon.net/2008/09/grails-logging/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Grails testing</title>
		<link>http://blog.sinequanon.net/2008/09/grails-testing/</link>
		<comments>http://blog.sinequanon.net/2008/09/grails-testing/#comments</comments>
		<pubDate>Tue, 23 Sep 2008 19:10:37 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[grails]]></category>

		<category><![CDATA[junit]]></category>

		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=58</guid>
		<description><![CDATA[The Grails docs talk about testing and have some example test methods but fail to describe some simple but necessary mechanics to get it going. The test methods should be in a class that extends GroovyTestCase (that word doesn&#8217;t appear at all when searching the Grails website). The class name must end with Tests since [...]]]></description>
		<wfw:commentRss>http://blog.sinequanon.net/2008/09/grails-testing/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Grails .gitignore</title>
		<link>http://blog.sinequanon.net/2008/09/grails-gitignore/</link>
		<comments>http://blog.sinequanon.net/2008/09/grails-gitignore/#comments</comments>
		<pubDate>Thu, 18 Sep 2008 19:14:06 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[git]]></category>

		<category><![CDATA[grails]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=49</guid>
		<description><![CDATA[I&#8217;ve started playing with git for source code revision management. Here is my first cut at a .gitignore for a Grails 1.0.3 project. Note that for previous versions you will also need (at least) a line /plugins/core


# .gitignore for Grails 1.0.3

# web application files that are overwritten by "grails upgrade"
#  cf. GRAILS_HOME/scripts/Upgrade.groovy, target( upgrade [...]]]></description>
		<wfw:commentRss>http://blog.sinequanon.net/2008/09/grails-gitignore/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Fluxbox startup and shutdown script</title>
		<link>http://blog.sinequanon.net/2008/09/fluxbox-startup-and-shutdown-script/</link>
		<comments>http://blog.sinequanon.net/2008/09/fluxbox-startup-and-shutdown-script/#comments</comments>
		<pubDate>Thu, 11 Sep 2008 18:50:29 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[fluxbox]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=28</guid>
		<description><![CDATA[The default Fluxbox startup file at ~/.fluxbox/startup is run by startfluxbox and has embedded comments describing how to add applications (&#34;apps&#34;) to run before Fluxbox starts up. The startup file can be fixed to also run apps after Fluxbox starts or after Fluxbox finishes. You might run apps after Fluxbox startup to be sure that [...]]]></description>
		<wfw:commentRss>http://blog.sinequanon.net/2008/09/fluxbox-startup-and-shutdown-script/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Hello, world (again)</title>
		<link>http://blog.sinequanon.net/2008/09/hello-world-again/</link>
		<comments>http://blog.sinequanon.net/2008/09/hello-world-again/#comments</comments>
		<pubDate>Thu, 11 Sep 2008 18:34:40 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[meta]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=30</guid>
		<description><![CDATA[So I&#8217;m trying this blog thing again. I never really got into it because I didn&#8217;t want to post a bunch of simple chatty stuff. Then I started noticing that my web searches were finding more answers on blogs than on archived email lists. Finally, Jared Richardson convinced me during his keynote Career 2.0 at [...]]]></description>
		<wfw:commentRss>http://blog.sinequanon.net/2008/09/hello-world-again/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
