<?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>The Lost Notebook &#187; wordpress</title>
	<atom:link href="http://funinc.org/tag/wordpress/feed" rel="self" type="application/rss+xml" />
	<link>http://funinc.org</link>
	<description>Things that I tend to forget</description>
	<lastBuildDate>Fri, 20 Jan 2012 14:42:07 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>CLI Blogging code</title>
		<link>http://funinc.org/20100209/cli-blogging-code</link>
		<comments>http://funinc.org/20100209/cli-blogging-code#comments</comments>
		<pubDate>Tue, 09 Feb 2010 09:09:22 +0000</pubDate>
		<dc:creator>abdallahdeeb</dc:creator>
				<category><![CDATA[Blogging]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://funinc.org/?p=241</guid>
		<description><![CDATA[Bookmark this category How it&#8217;s done. I started out with a bash function as described earlier. The function code is below: function blog() { echo "$2" &#124; mail -s "$1" address@example.com; } Then I noticed I would need more freedom to write longer text, without leaving the shell. So here goes the &#8220;blog&#8221; bash script. [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://funinc.org/category/blogging/">Bookmark this category</a><br />
How it&#8217;s done. I started out with a bash function as described earlier. The function code is below:<br />
<code>function blog() { echo "$2" | mail -s "$1" address@example.com; }</code></p>
<p> Then I noticed I would need more freedom to write longer text, without leaving the shell. So here goes the &#8220;blog&#8221; bash script. I&#8217;m using the postie wordpress plugin on the server side, so things are a bit more manageable. I may add more to this later if I get time.</p>
<p><code>#!/bin/bash<br />
if [ -n "$2" ]; then<br />
   BODY=$2<br />
else<br />
   vi tmpfile; BODY=`cat tmpfile`; rm tmpfile<br />
fi<br />
if [ -n "$1" ]; then<br />
   SUBJECT=$1<br />
else<br />
   echo -n "Subject:"; read SUBJECT<br />
fi<br />
echo "$BODY" | mail -s "$SUBJECT" address@example.com<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://funinc.org/20100209/cli-blogging-code/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress + SVN + Auto-update</title>
		<link>http://funinc.org/20091223/wordpress-svn-auto-update</link>
		<comments>http://funinc.org/20091223/wordpress-svn-auto-update#comments</comments>
		<pubDate>Wed, 23 Dec 2009 09:57:10 +0000</pubDate>
		<dc:creator>abdallah</dc:creator>
				<category><![CDATA[Blogging]]></category>
		<category><![CDATA[Coding]]></category>
		<category><![CDATA[Work]]></category>
		<category><![CDATA[auto-update]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[permissions]]></category>
		<category><![CDATA[svn]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://funinc.org/20091223/wordpress-extra-settings.moo/</guid>
		<description><![CDATA[I&#8217;ve been using the latest cutting edge wordpress from svn for a while now and it&#8217;s been good. At the time of the writing You are using WordPress 3.0-alpha. Basically, even the latest code is safe(ish) and things don&#8217;t break easily. I&#8217;m not using it for &#8220;production&#8221; per se, as the only other person who [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been using the latest cutting edge wordpress from svn for a while now and it&#8217;s been good. At the time of the writing</p>
<blockquote><p>You are using WordPress 3.0-alpha.  </p></blockquote>
<p>Basically, even the latest code is safe(ish) and things don&#8217;t break easily.</p>
<p>I&#8217;m not using it for &#8220;production&#8221; per se, as the only other person who ever reads this blog is probably me!</p>
<p>So, here&#8217;s how I do it:</p>
<p><code>svn up</code></p>
<p>If you expected more, there&#8217;s really not much there. As everything is pretty simple to setup as per the notes in http://codex.wordpress.org/Installing/Updating_WordPress_with_Subversion</p>
<p>Some would only want to update to &#8220;stable&#8221; version. Others, like me will follow the absolute latest.</p>
<p>Now, how about the permissions for the directory where wordpress is setup. Here&#8217;s what I use:</p>
<blockquote><p>my username: wpuser</p>
<p>apache user: nobody</p>
<p>wordpress installation directory: /home/wpuser/public_html/</p></blockquote>
<p><code>cd /home/wpuser/public_html</p>
<p>chown -R wpuser:nobody</p>
<p>find . -type d -exec chmod 755 {} \;</p>
<p>find . -type f -exec chmod 644 {} \;</p>
<p></code></p>
<p>With the above, it&#8217;s easy to upgrade simply by going:</p>
<p><code>su wpuser</p>
<p>svn up</code></p>
<p>Now, the automatic upgrade/setup for plugins should work perfectly from within wordpress&#8217; admin interface. If it doesn&#8217;t you might want to add the following in wp-config.php:</p>
<p><code lang="php">// Additional variables to allow auto update</p>
<p>define('FS_CHMOD_FILE',0644);</p>
<p>define('FS_CHMOD_DIR',0755);</p>
<p>define('FS_METHOD', 'direct');</p>
<p></code></p>
<p>I hope this helps someone out there. Give me a shout if it does <img src='http://funinc.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://funinc.org/20091223/wordpress-svn-auto-update/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

