summaryrefslogtreecommitdiffstats
path: root/owning-blogosphere.rst
diff options
context:
space:
mode:
authorMatěj Cepl <mcepl@cepl.eu>2016-02-08 22:28:13 +0100
committerMatěj Cepl <mcepl@cepl.eu>2016-02-08 22:28:13 +0100
commiteb8374e2cc8776288b190f74e2a2e39284d0c6ef (patch)
tree2b41c206b516c87aa0ca9ece7df295a49cb75246 /owning-blogosphere.rst
parente653b49c3738fc96b598d94cbb356fc2172f6ea9 (diff)
downloadblog-source-eb8374e2cc8776288b190f74e2a2e39284d0c6ef.tar.gz
Add owning-blogosphere post
Diffstat (limited to 'owning-blogosphere.rst')
-rw-r--r--owning-blogosphere.rst58
1 files changed, 58 insertions, 0 deletions
diff --git a/owning-blogosphere.rst b/owning-blogosphere.rst
new file mode 100644
index 0000000..bc2cbd0
--- /dev/null
+++ b/owning-blogosphere.rst
@@ -0,0 +1,58 @@
+On owning blogosphere
+#####################
+
+:date: 2016-01-27T13:16:07
+:category: computer
+:tags: owncloud, blog, pelican
+
+(originally comment on blogpost_ by Dave Winner)
+
+I was thinking about this a lot especially from the point of view of
+owning my own data. The first version of how to do it was “the canonical
+version is on my harddrive in some reasonable format, WordPress is just
+for presentation to be discarded anytime” (even more important because
+WP pulverizes anything resembling HTML into its own disgusting mush).
+For that I started to use (and extended) `b.py`_ (with reStructuredText_
+sources; originally from elsewhere_, but upstream didn’t accepted my
+changes) and used WP on `my own server`_.
+
+Then inevitable happened: my server died, so I have to rebuild my
+site. My colleagues from work shared rented VPS so I joined them
+and pointed my domain to it. However, when I started to work on
+installing WP, I was caught again by my suspicions about WP. Do I
+really want to fight with pulverized HTML, zillion upgrades,
+comment spam, etc., when all I want from the server is to render
+my posts to HTML? So, I started to look for static web
+generators. After a brief affair with Hexo_ (Server-side
+JavaScript looks like such a good idea, but it still so immature
+and unuseable!) I ended up with pelican_.
+
+The only problem is of course the only dynamic part of my blog,
+which are comments. For now I have Disqus on my site as everybody
+else, but I am very unhappy with it. Sometimes, when I have time
+I will try to make Isso_ working for me, but I have failed so
+far.
+
+.. _blogpost:
+ http://scripting.com/liveblog/users/davewiner/2016/01/26/0934.html
+
+.. _`b.py`:
+ https://gitlab.com/mcepl/b.py
+
+.. _elsewhere:
+ http://bitbucket.org/livibetter/b.py
+
+.. _reStructuredText:
+ http://docutils.sourceforge.net/docs/ref/rst/introduction.html
+
+.. _`my own server`:
+ http://scripting.com/stories/2010/07/08/peopleHostingTheirOwnServe.html
+
+.. _Hexo:
+ https://hexo.io/
+
+.. _pelican:
+ http://blog.getpelican.com/
+
+.. _Isso:
+ https://posativ.org/isso/