<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Blogofile on Sirius Stuff</title>
    <link>https://www.siriusventures.com/tags/blogofile/</link>
    <description>Recent content in Blogofile on Sirius Stuff</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 29 Oct 2020 01:01:01 -0700</lastBuildDate>
    <atom:link href="https://www.siriusventures.com/tags/blogofile/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Moving from Blogofile to Pelican</title>
      <link>https://www.siriusventures.com/moving-from-blogofile-to-pelican/</link>
      <pubDate>Thu, 29 Oct 2020 01:01:01 -0700</pubDate>
      <guid>https://www.siriusventures.com/moving-from-blogofile-to-pelican/</guid>
      <description>&lt;p&gt;A couple of years after I &lt;a href=&#34;https://www.siriusventures.com/switched-from-wordpress-to-blogofile/&#34;&gt;wrote&lt;/a&gt; about how happy I was with Blogofile, it stopped being developed.  The &lt;a href=&#34;https://github.com/EnigmaCurry/blogofile&#34;&gt;last update&lt;/a&gt; on GitHub was in 2015, the owner has archived the repository, and Blogofile.com doesn&amp;rsquo;t answer anymore.&lt;/p&gt;
&lt;p&gt;I looked for forks and didn&amp;rsquo;t find any active ones.  So as much as I liked the look and feel of my blog, it was going to have to switch software to something that was supported.  I looked at several different options but the only one written in Python that seemed active was &lt;a href=&#34;https://blog.getpelican.com&#34;&gt;Pelican&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Script to Update Blogofile Blog on Amazon S3</title>
      <link>https://www.siriusventures.com/script-to-update-blogofile-blog-on-amazon-s3/</link>
      <pubDate>Fri, 29 Apr 2011 16:00:10 -0700</pubDate>
      <guid>https://www.siriusventures.com/script-to-update-blogofile-blog-on-amazon-s3/</guid>
      <description>&lt;p&gt;Because &lt;a href=&#34;https://www.blogofile.com&#34;&gt;Blogofile&lt;/a&gt;(at least the 0.7.1 version I&amp;rsquo;m using) regenerates every file and directory every time it makes it hard to update just the changed files on &lt;a href=&#34;https://www.amazon.com/&#34;&gt;Amazon&lt;/a&gt;&amp;rsquo;s &lt;a href=&#34;https://aws.amazon.com/s3/&#34;&gt;S3&lt;/a&gt; (Simple Storage System) can scale incredibly high&lt;/p&gt;
&lt;p&gt;So I wrote a shell script that updates only the changed files and also pings &lt;a href=&#34;https://www.googleping.com/&#34;&gt;GooglePing&lt;/a&gt; so that Google and other services come along and read your update.&lt;/p&gt;
&lt;p&gt;Over time, the difference between what the old page 2 on S3 has and what it should be will build. There&amp;rsquo;s a simple answer, which is to just upload all of the page files.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What&#39;s not perfect with Blogofile</title>
      <link>https://www.siriusventures.com/whats-not-perfect-with-blogofile/</link>
      <pubDate>Thu, 28 Apr 2011 15:00:10 -0700</pubDate>
      <guid>https://www.siriusventures.com/whats-not-perfect-with-blogofile/</guid>
      <description>&lt;p&gt;In &lt;a href=&#34;https://www.siriusventures.com/switched-from-wordpress-to-blogofile&#34;&gt;Switched from WordPress to Blogofile&lt;/a&gt; there are two good things about using Blogofile:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;flat files are almost impossible to hack&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.amazon.com/&#34;&gt;Amazon&lt;/a&gt;&amp;rsquo;s &lt;a href=&#34;https://aws.amazon.com/s3/&#34;&gt;S3&lt;/a&gt; (Simple Storage System) can scale incredibly high&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There&amp;rsquo;s some downsides:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;blogofile build seems to copy or regenerate every single file&lt;/li&gt;
&lt;li&gt;it&amp;rsquo;s not totally happy being on S3 - it doesn&amp;rsquo;t make index.html files for the archive and category directories.&lt;/li&gt;
&lt;li&gt;there&amp;rsquo;s no easy way to post-via-email or send a link to start a post&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Right now I&amp;rsquo;m writing this with vi and that&amp;rsquo;s far less comfortable than WordPress&amp;rsquo;s editor which I really liked. But I&amp;rsquo;m sure I&amp;rsquo;ll find TextWrangler or something as suitable for writing blog posts.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Switched from WordPress to Blogofile</title>
      <link>https://www.siriusventures.com/switched-from-wordpress-to-blogofile/</link>
      <pubDate>Thu, 28 Apr 2011 13:24:10 -0700</pubDate>
      <guid>https://www.siriusventures.com/switched-from-wordpress-to-blogofile/</guid>
      <description>&lt;p&gt;I really like &lt;a href=&#34;https://www.wordpress.org/&#34;&gt;WordPress&lt;/a&gt; for the huge number of themes and utilities that it has. What I don&amp;rsquo;t like, though, is the need for constant vigilance to make sure that your blog hasn&amp;rsquo;t been hacked. When I started the conversion, I found two blog posts that had been secretly altered so that they had links to spam sites. I wasn&amp;rsquo;t sure whether to be grateful that only two had been altered or disappointed that my blog mattered so little that that&amp;rsquo;s all they did.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
