summaryrefslogtreecommitdiffstats
path: root/src/journal
diff options
context:
space:
mode:
authorJohannes Löthberg <johannes@kyriasis.com>2014-10-21 15:28:18 +0200
committerJohannes Löthberg <johannes@kyriasis.com>2014-10-21 15:28:18 +0200
commitaf83ac9fdf13c670f4a5a2b7f68753c67ab27f2f (patch)
treee9eeed4ba43ad4f74b41d77dabf30d8532f539fd /src/journal
parent3a703d05efc4536dab7b21fb702253238a01666e (diff)
downloadwebsite-af83ac9fdf13c670f4a5a2b7f68753c67ab27f2f.tar.xz
hardwrap all journal entries
Diffstat (limited to 'src/journal')
-rw-r--r--src/journal/1-hello-world.rst12
-rw-r--r--src/journal/2-comments.rst50
-rw-r--r--src/journal/3-atom-feed.rst14
-rw-r--r--src/journal/4-comment-moderation.rst10
4 files changed, 71 insertions, 15 deletions
diff --git a/src/journal/1-hello-world.rst b/src/journal/1-hello-world.rst
index b5827a4..444896a 100644
--- a/src/journal/1-hello-world.rst
+++ b/src/journal/1-hello-world.rst
@@ -4,9 +4,17 @@
author: Johannes Löthberg
author_link: /~kyrias/about.html
-I should probably write an entry some time. I’ve been thinking about what to write about for a while but I can’t really think of anything that I’d want people to read. (Not that I expect anyone to actually read this, eh…) Could write about what I’m doing and how I’m poking and prodding at this site maybe? Or maybe something related to LDAP, or setting up OpenSMTPD and Dovecot, or maybe bind, or even Kerberos… All of them could be useful for future reference for myself in either case I guess.
+I should probably write an entry some time. I’ve been thinking about what to
+write about for a while but I can’t really think of anything that I’d want
+people to read. (Not that I expect anyone to actually read this, eh…) Could
+write about what I’m doing and how I’m poking and prodding at this site maybe?
+Or maybe something related to LDAP, or setting up OpenSMTPD and Dovecot, or
+maybe bind, or even Kerberos… All of them could be useful for future reference
+for myself in either case I guess.
-It’s almost 02:00 as I’m writing this though, so I should probably be getting to bed. I sort of feel like skipping school tomorrow though, at least the first lesson maybe, since I’m very unlikely to wake up in time even if I try…
+It’s almost 02:00 as I’m writing this though, so I should probably be getting
+to bed. I sort of feel like skipping school tomorrow though, at least the first
+lesson maybe, since I’m very unlikely to wake up in time even if I try…
Anyway, bonum nocte…
diff --git a/src/journal/2-comments.rst b/src/journal/2-comments.rst
index 7dffe53..e983249 100644
--- a/src/journal/2-comments.rst
+++ b/src/journal/2-comments.rst
@@ -4,17 +4,48 @@
author: Johannes Löthberg
author_link: /~kyrias/about.html
-Finally set it up so that each journal entry gets a separate page generated for itself too in addition to being on the `journal index`_. Each entry gets a file in the ``/~kyrias/journal/`` subdirectory named after the entry source file but with the extension changed to ``.html`` instead of ``.rst``.
+Finally set it up so that each journal entry gets a separate page generated for
+itself too in addition to being on the `journal index`_. Each entry gets a file
+in the ``/~kyrias/journal/`` subdirectory named after the entry source file but
+with the extension changed to ``.html`` instead of ``.rst``.
-My first thought for which commenting system to use was disqus, but I don't really like using it at all in practice so I quickly decided against it. I do quite like discourse_ though and thought about setting it up, but that would require me setting up PostgreSQL and Redis, neither of which I feel like setting up nor that I would have any other use for, and both would use up quite a bit of resources for basically nothing, so discourse was out.
+My first thought for which commenting system to use was disqus, but I don't
+really like using it at all in practice so I quickly decided against it. I do
+quite like discourse_ though and thought about setting it up, but that would
+require me setting up PostgreSQL and Redis, neither of which I feel like
+setting up nor that I would have any other use for, and both would use up quite
+a bit of resources for basically nothing, so discourse was out.
-After looking around for a bit and finding a few disqus clones I finally found isso_, which is named after either a German abbreviation or after the 360th_ Pokémon’s name in German. While it’s probably the first alternative, the second sounds more fun so I’ll just go with that.
+After looking around for a bit and finding a few disqus clones I finally found
+isso_, which is named after either a German abbreviation or after the 360th_
+Pokémon’s name in German. While it’s probably the first alternative, the second
+sounds more fun so I’ll just go with that.
-Isso is a rather simple commenting server written in python, uses Markdown for stylinx (hopefully I can get it to do reStructuredText too maybe), and using SQLite for storage which is a plus since it means I don't have to set up some big bulky SQL server. All you need to do to try it out is on the `quickstart page`_, but it roughly comes down to first installing isso (it’s installable through ``pip``), then writing a really short config file that tells isso where to store the SQLite database for comments and which hosts isso will be used on for CORS_. After that you just start isso up pointing it at the config file and it’s up and running. The client-side of isso is just ``script`` and ``section`` tag away, and then you’re done setting it up.
+Isso is a rather simple commenting server written in python, uses Markdown for
+stylinx (hopefully I can get it to do reStructuredText too maybe), and using
+SQLite for storage which is a plus since it means I don't have to set up some
+big bulky SQL server. All you need to do to try it out is on the `quickstart
+page`_, but it roughly comes down to first installing isso (it’s installable
+through ``pip``), then writing a really short config file that tells isso where
+to store the SQLite database for comments and which hosts isso will be used on
+for CORS_. After that you just start isso up pointing it at the config file and
+it’s up and running. The client-side of isso is just ``script`` and ``section``
+tag away, and then you’re done setting it up.
-Isso has support for simple moderation where new comments end up in a queue and has to be manually activated by going through a URL that can be emailed to you if you want, and things like rate limiting new comments. All of it is documented on the `server configuration`_ and `client configuration`_ pages, and there's also some info on the isso API and things like a comment counter. I could continue rambling about what it supports, but that would be rather pointless since it’s written so nicely on their website.
+Isso has support for simple moderation where new comments end up in a queue and
+has to be manually activated by going through a URL that can be emailed to you
+if you want, and things like rate limiting new comments. All of it is
+documented on the `server configuration`_ and `client configuration`_ pages,
+and there's also some info on the isso API and things like a comment counter. I
+could continue rambling about what it supports, but that would be rather
+pointless since it’s written so nicely on their website.
-Where I had some issues was getting it run properly under uWSGI_ and using NGINX_ as a reverse proxy, but it turned out after an hour of testing that I had installed uWSGI but not the python plugin. D’oh. Once I had that installed and added ``plugins = python`` to the uWSGI config file and adjusted my NGINX config file slightly since I run isso under a sub URI instead of on a separate domain it worked perfectly though.
+Where I had some issues was getting it run properly under uWSGI_ and using
+NGINX_ as a reverse proxy, but it turned out after an hour of testing that I
+had installed uWSGI but not the python plugin. D’oh. Once I had that installed
+and added ``plugins = python`` to the uWSGI config file and adjusted my NGINX
+config file slightly since I run isso under a sub URI instead of on a separate
+domain it worked perfectly though.
Here’s the config files I’m currently using:
@@ -22,9 +53,12 @@ Here’s the config files I’m currently using:
<script src="https://gist.github.com/kyrias/f7ec681e1c8c2effdb7e.js"></script>
-As far as I know the ``uwsgi_param HTTP_X_SCRIPT_NAME /isso;`` line is only needed if you’re running isso under a sub URI and I think it isn’t needed if you aren’t, but don’t quite me on that.
+As far as I know the ``uwsgi_param HTTP_X_SCRIPT_NAME /isso;`` line is only
+needed if you’re running isso under a sub URI and I think it isn’t needed if
+you aren’t, but don’t quite me on that.
-I have yet to set up the moderation part of isso though, and that’s probably what I’m going to play with next.
+I have yet to set up the moderation part of isso though, and that’s probably
+what I’m going to play with next.
geros ilas.
diff --git a/src/journal/3-atom-feed.rst b/src/journal/3-atom-feed.rst
index 17fbaa7..77da8d3 100644
--- a/src/journal/3-atom-feed.rst
+++ b/src/journal/3-atom-feed.rst
@@ -4,11 +4,19 @@
author: Johannes Löthberg
author_link: /~kyrias/about.html
-Added an atom generator thingy to ``bupa``, (short for “build page”,) which is a python script I use to generate this website. The script uses docutils for parsing the body text written in reStructuredText_ and uses jinja2_ templates to stuff the body text into. The atom feed is generated using pyatom at the same time as the separate journal entry pages are written out.
+Added an atom generator thingy to ``bupa``, (short for “build page”,) which is
+a python script I use to generate this website. The script uses docutils for
+parsing the body text written in reStructuredText_ and uses jinja2_ templates
+to stuff the body text into. The atom feed is generated using pyatom at the
+same time as the separate journal entry pages are written out.
-Was rather easy to do, tho I’m unsure if I’ll keep it since it’s rather pointless.
+Was rather easy to do, tho I’m unsure if I’ll keep it since it’s rather
+pointless.
-A more important thing to focus on would probably be making ``bupa`` a more general script instead so there’s less duplication maybe.. Especially since the theos_ website is also built using a copy of the same script, but slightly modified.
+A more important thing to focus on would probably be making ``bupa`` a more
+general script instead so there’s less duplication maybe.. Especially since the
+theos_ website is also built using a copy of the same script, but slightly
+modified.
co'o
diff --git a/src/journal/4-comment-moderation.rst b/src/journal/4-comment-moderation.rst
index 39fa1ea..00cdd06 100644
--- a/src/journal/4-comment-moderation.rst
+++ b/src/journal/4-comment-moderation.rst
@@ -4,8 +4,14 @@
author: Johannes Löthberg
author_link: /~kyrias/about.html
-Enabled comment moderation in isso today, and it seems to work rather well. It emails you two links, one to delete the comment and one to activate it. After the comment has been deleted or activated you just get a blank page though, so I wonder how hard it’d be to get isso to redirect you to the journal entry page instead.
+Enabled comment moderation in isso today, and it seems to work rather well. It
+emails you two links, one to delete the comment and one to activate it. After
+the comment has been deleted or activated you just get a blank page though, so
+I wonder how hard it’d be to get isso to redirect you to the journal entry page
+instead.
-Even nicer would be having an admin interface to manage both new and old comments, and there’s been an issue_ open about it since almost a year ago, and hopefully someone will work on it eventually.
+Even nicer would be having an admin interface to manage both new and old
+comments, and there’s been an issue_ open about it since almost a year ago, and
+hopefully someone will work on it eventually.
.. _issue: https://github.com/posativ/isso/issues/10