<?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>fak3r &#187; howto</title>
	<atom:link href="http://fak3r.com/tag/howto/feed/" rel="self" type="application/rss+xml" />
	<link>http://fak3r.com</link>
	<description>look out honey, &#039;cause I&#039;m using technology</description>
	<lastBuildDate>Sat, 11 Feb 2012 05:25:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Ruby on Rails: gem install versus apt-get</title>
		<link>http://fak3r.com/2009/11/18/ruby-on-rails-gem-install-versus-apt-get/</link>
		<comments>http://fak3r.com/2009/11/18/ruby-on-rails-gem-install-versus-apt-get/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 17:09:35 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[apt-get]]></category>
		<category><![CDATA[bsd]]></category>
		<category><![CDATA[config]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[gem install]]></category>
		<category><![CDATA[hacker]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[redmine]]></category>
		<category><![CDATA[ruby]]></category>
		<category><![CDATA[ruby on rails]]></category>
		<category><![CDATA[update]]></category>

		<guid isPermaLink="false">http://fak3r.com/?p=1850</guid>
		<description><![CDATA[

UPDATE: Thanks to Ryan, Ant and Fern for the tips.  With that in mind I found an online Slicehost tutorial that contained the steps and explained how to install ruby via apt-get, then get the latest rubygems, install that manually, ran gem to update itself, then run gem to install rails &#8211; as suggested.  The [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2009/11/18/ruby-on-rails-gem-install-versus-apt-get/feed/</wfw:commentRss>
		<slash:comments>20</slash:comments>
		</item>
		<item>
		<title>HOWTO build your own open source Dropbox clone</title>
		<link>http://fak3r.com/2009/09/14/howto-build-your-own-open-source-dropbox-clone/</link>
		<comments>http://fak3r.com/2009/09/14/howto-build-your-own-open-source-dropbox-clone/#comments</comments>
		<pubDate>Tue, 15 Sep 2009 04:21:03 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[diy]]></category>
		<category><![CDATA[dropbox]]></category>
		<category><![CDATA[mirror]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[sync]]></category>

		<guid isPermaLink="false">http://fak3r.com/?p=1727</guid>
		<description><![CDATA[


UPDATE #4 It&#8217;s 2012, and this project is still alive, although I haven&#8217;t worked on lipsync as much as I should.  I want to, and have new ideas to implement and try out in the next few months. The two way sharing is a bit hacky, and I don&#8217;t like it, the installer creates a [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2009/09/14/howto-build-your-own-open-source-dropbox-clone/feed/</wfw:commentRss>
		<slash:comments>321</slash:comments>
		</item>
		<item>
		<title>HOWTO: log the user&#039;s IP, not the proxy&#039;s, in nginx access log</title>
		<link>http://fak3r.com/2008/12/18/howto-log-the-user%e2%80%99s-ip-not-the-proxy%e2%80%99s-in-nginx-access-log/</link>
		<comments>http://fak3r.com/2008/12/18/howto-log-the-user%e2%80%99s-ip-not-the-proxy%e2%80%99s-in-nginx-access-log/#comments</comments>
		<pubDate>Thu, 18 Dec 2008 18:55:27 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[lighttpd]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[varnish]]></category>

		<guid isPermaLink="false">http://www.fak3r.com/?p=1280</guid>
		<description><![CDATA[So back in January I had a post about HOWTO: log the user&#8217;s IP, not the proxy&#8217;s, in Lighttpd access log, but today I switched that system to run nginx (actually nginx has been running since early this year, I just got lazy on running Varnish) fronted again by Varnish.  I had the same [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2008/12/18/howto-log-the-user%e2%80%99s-ip-not-the-proxy%e2%80%99s-in-nginx-access-log/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>HOWTO: install Ruby on Rails on Debian or Ubuntu Linux easily</title>
		<link>http://fak3r.com/2008/10/29/howto-install-ruby-on-rails-on-debian-or-ubuntu-linux-easily/</link>
		<comments>http://fak3r.com/2008/10/29/howto-install-ruby-on-rails-on-debian-or-ubuntu-linux-easily/#comments</comments>
		<pubDate>Wed, 29 Oct 2008 23:07:59 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[clouds]]></category>
		<category><![CDATA[CouchDB]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[debian gnu]]></category>
		<category><![CDATA[drupal]]></category>
		<category><![CDATA[gnu linux]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[newrailsapp]]></category>
		<category><![CDATA[ruby]]></category>
		<category><![CDATA[ruby on rails]]></category>
		<category><![CDATA[rubygems]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[Typo]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[ubuntu linux]]></category>
		<category><![CDATA[WEBrick]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.fak3r.com/?p=1138</guid>
		<description><![CDATA[In the early days of this blog I used to run it on Typo, which *was* a great Ruby on Rails blogging platform (at one time).  Unfortunately the project stalled (for years) and I ended up jumping ship after a few months of bugs and the ever crashing Rails server, WEBrick.  Yes, if you search [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2008/10/29/howto-install-ruby-on-rails-on-debian-or-ubuntu-linux-easily/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>HOWTO: webserver in 100 lines of Bash</title>
		<link>http://fak3r.com/2008/09/04/howto-webserver-in-100-lines-of-bash/</link>
		<comments>http://fak3r.com/2008/09/04/howto-webserver-in-100-lines-of-bash/#comments</comments>
		<pubDate>Fri, 05 Sep 2008 00:48:38 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[netcat]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[perl]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[webserver]]></category>
		<category><![CDATA[www]]></category>

		<guid isPermaLink="false">http://fak3r.com/?p=955</guid>
		<description><![CDATA[I&#8217;m a big Bash fan, I know Perl is the more popular scripting language, and I&#8217;m slowly using it more, but hey, if I need something done, I can do it quicker in Bash (keeping in mind that I&#8217;m a systems guy, not a dev guy).  While at work looking up Bash related syntax [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2008/09/04/howto-webserver-in-100-lines-of-bash/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>HOWTO: conky config (conkyrc) for Debian Part 2</title>
		<link>http://fak3r.com/2008/08/26/howto-conky-config-conkyrc-for-debian-part-2/</link>
		<comments>http://fak3r.com/2008/08/26/howto-conky-config-conkyrc-for-debian-part-2/#comments</comments>
		<pubDate>Tue, 26 Aug 2008 22:45:50 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[config]]></category>
		<category><![CDATA[conky]]></category>
		<category><![CDATA[conky config]]></category>
		<category><![CDATA[conkyrc]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[lightweight desktop]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[openbox]]></category>

		<guid isPermaLink="false">http://fak3r.com/?p=916</guid>
		<description><![CDATA[I changed around my Conky config, and it&#8217;s something you could do forever, but it&#8217;s great because it can be as heavy or light as you want it.  Recently I dropped Gnome almost all together to run Openbox (full HOWTO on this forthcoming).  I found a panel that will house things like nm-applet [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2008/08/26/howto-conky-config-conkyrc-for-debian-part-2/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>HOWTO: recursively download only specific file types</title>
		<link>http://fak3r.com/2008/07/28/howto-recursively-download-only-specific-file-types/</link>
		<comments>http://fak3r.com/2008/07/28/howto-recursively-download-only-specific-file-types/#comments</comments>
		<pubDate>Mon, 28 Jul 2008 18:04:29 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[music]]></category>
		<category><![CDATA[download]]></category>
		<category><![CDATA[grab]]></category>
		<category><![CDATA[mp3]]></category>
		<category><![CDATA[snarf]]></category>
		<category><![CDATA[wget]]></category>

		<guid isPermaLink="false">http://fak3r.com/?p=838</guid>
		<description><![CDATA[Have you ever found a batch of mp3s online on someone&#8217;s &#8216;Index of&#8217; page?  I know you have (and if not, do a search for &#8216;google hacks&#8217; in google to learn about the fun)  The issue always comes up that I find an album I want to grab, but the individual files are in a [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2008/07/28/howto-recursively-download-only-specific-file-types/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HOWTO: conky config (conkyrc) for Debian</title>
		<link>http://fak3r.com/2008/07/01/howto-conky-config-conkyrc-for-debian/</link>
		<comments>http://fak3r.com/2008/07/01/howto-conky-config-conkyrc-for-debian/#comments</comments>
		<pubDate>Wed, 02 Jul 2008 00:44:09 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[desktop]]></category>
		<category><![CDATA[gadget]]></category>
		<category><![CDATA[how to]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[monitor]]></category>
		<category><![CDATA[widet]]></category>

		<guid isPermaLink="false">http://www.fak3r.com/?p=781</guid>
		<description><![CDATA[If you run a Linux desktop you need to be using conky.  It compiles all those shiny gadget you see on other desktops eating system RAM, down to what you need; information on what your system is doing.  So try it out, install conky, and then drop this into your home directory as .conkyrc &#8211; [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2008/07/01/howto-conky-config-conkyrc-for-debian/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>HOWTO: use monit to keep Lighttpd and Varnish running</title>
		<link>http://fak3r.com/2008/02/19/howto-use-monit-to-keep-lighttpd-and-varnish-running/</link>
		<comments>http://fak3r.com/2008/02/19/howto-use-monit-to-keep-lighttpd-and-varnish-running/#comments</comments>
		<pubDate>Tue, 19 Feb 2008 19:51:00 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[lighttpd]]></category>
		<category><![CDATA[varnish]]></category>

		<guid isPermaLink="false">http://www.fak3r.com/2008/02/19/howto-use-monit-to-keep-lighttpd-and-varnish-running/</guid>
		<description><![CDATA[Thanks to a post from Steve over at debian-administration.org, I finally got around to setting up monit, the little monitoring app we use at work to keep things sane.  I was getting around to installing it at home, but it became more urgent when Varnish went down last week; without it running there&#8217;s nothing to [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2008/02/19/howto-use-monit-to-keep-lighttpd-and-varnish-running/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>HOWTO: log the user&#039;s IP, not the proxy&#039;s, in Lighttpd access log</title>
		<link>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/</link>
		<comments>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/#comments</comments>
		<pubDate>Wed, 09 Jan 2008 16:17:41 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[access log]]></category>
		<category><![CDATA[http accelerator]]></category>
		<category><![CDATA[IP]]></category>
		<category><![CDATA[lighttpd]]></category>
		<category><![CDATA[lighty]]></category>
		<category><![CDATA[referring]]></category>
		<category><![CDATA[reverse proxy]]></category>
		<category><![CDATA[squid]]></category>
		<category><![CDATA[varnish]]></category>
		<category><![CDATA[x-forwarded-for]]></category>

		<guid isPermaLink="false">http://fak3r.com/2008/01/09/howto-log-users-ip-not-the-proxys-in-lighttpd-access-log/</guid>
		<description><![CDATA[When you run a webserver behind a reverse proxy or HTTP accelerator like Squid or Varnish, the webserver access logs will display the IP of the proxy (generally 127.0.0.1) instead of the end user&#8217;s IP.  This not only breaks any kind of tracking or reporting you want to run against your webserver logs, but it [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
	</channel>
</rss>

