<?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>n8blog &#187; blosxom</title>
	<atom:link href="http://www.n8gray.org/blog/category/blogging/blosxom/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.n8gray.org</link>
	<description>distraction in action</description>
	<lastBuildDate>Thu, 01 Jul 2010 18:21:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Blosxom Permissions and Directories on OS X</title>
		<link>http://www.n8gray.org/blog/2004/06/02/blosxom-permissions-and-directories-on-os-x/</link>
		<comments>http://www.n8gray.org/blog/2004/06/02/blosxom-permissions-and-directories-on-os-x/#comments</comments>
		<pubDate>Wed, 02 Jun 2004 10:13:00 +0000</pubDate>
		<dc:creator>n8</dc:creator>
				<category><![CDATA[blosxom]]></category>

		<guid isPermaLink="false">http://www.n8gray.org/sandbox/wordpress/?p=77</guid>
		<description><![CDATA[Mac OS X Hints recently had a
useful hint about adding a preview pane to Blosxom writebacks.  (Yes, I&apos;ll
be implementing that at some point&#8230; ;^)  In the discussion that followed,
some people posted some comments about setting up Blosxom on OS X that struck
me as a bit misinformed.  In particular, people didn&apos;t seem to [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.macosxhints.com">Mac OS X Hints</a> recently had <a href="http://www.macosxhints.com/article.php?story=20040527154619100#comments">a
useful hint</a> about adding a preview pane to Blosxom writebacks.  (Yes, I&apos;ll<br />
be implementing that at some point&#8230; ;^)  In the discussion that followed,<br />
some people posted some comments about setting up Blosxom on OS X that struck<br />
me as a bit misinformed.  In particular, people didn&apos;t seem to know what files<br />
needed to be <em>readable</em> by the web server user (user: <code>www</code>,<br />
group: <code>www</code>) and what files needed to be <em>writable</em><br />
(usually owned) by that user.  Also, people seemed to be under the impression<br />
that they should put the raw <code>.txt</code> files inside their website&apos;s<br />
directory hierarchy, which is probably not wise.

<p>Here&apos;s the breakdown.  These files just need to be <em>readable</em> by
<code>www:www</code>:<br />
<ul>
    <li>Blog entries (usually <code>.txt</code> files)
    <li>Flavour files
    <li>Plugins
</ul>

<p>Therefore, these files can live <em>anywhere</em> as long as the
<code>www</code> user has read access.  I put them in<br />
<code>/Users/n8gray/web/blosxom</code>, which I made readable by all users.

<p>There&apos;s usually only one directory that needs to be writable by the web
server: The plugin state directory.  You want to make sure, however, that only<br />
you and <code>www</code> are able to write there.  One easy way to do this is<br />
to make the plugin state directory owned by you, but with group www.  Then make<br />
it both owner and group writable (Permissions 775, or drwxrwxr-x).  I use the <br />
directory <code>/Users/n8gray/web/blosxom/plugins/state</code> for plugins.

<p>One thing to note is that <em>none</em> of these files are under
<code>/Users/n8gray/Sites</code> or <code>/Library/WebServer</code>.  Putting<br />
them in those directories would potentially allow strangers to read raw files<br />
or activate plugins directly from their browsers, which is probably<br />
undesirable.  We want all access to the blog content to be through the<br />
<code>blosxom.cgi</code> script.  Therefore, <code>blosxom.cgi</code> should be<br />
the <em>only</em> part of the Blosxom system that lives in a<br />
publicly-accessible area (something like <code>~/Sites/cgi-bin</code>).

<p>Finally, I don&apos;t claim that this is the best or only way to set up Blosxom
under OS X.  I do, however, think that this is a sensible way to set it up. <br />
Leave a comment if you have a better idea!<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.n8gray.org%2Fblog%2F2004%2F06%2F02%2Fblosxom-permissions-and-directories-on-os-x%2F&amp;linkname=Blosxom%20Permissions%20and%20Directories%20on%20OS%20X"><img src="http://www.n8gray.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.n8gray.org/blog/2004/06/02/blosxom-permissions-and-directories-on-os-x/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

