Blorgit: Org-Mode based, git amenable, blogging engine

1. In Browser Editing Org-mode files can be edited through the browser. Upon submitting an edit the original org-mode file is overwritten and the web-page is re-exported. Edits can be turned on off or with the editable configuration option and can be password protected by setting the auth configuration option
2. Export to org-mode and LaTeX formats The raw Org-mode source, and LaTeX exports of all pages can be downloaded.
3. Search The search bar compares your search terms as a perl-style regular expression (in most cases working just like a simple term search) against the org-mode source of each page returning a ranked list.
4. Sidebar with Recent changes and Directory Listing The top N recently edited pages, and/or directory listings can optionally be presented in a sidebar. These are controlled through the recent and dir_list configuration options.
5. Themes The blorgit_themes git repository holds prepackaged themes for blorgit. These can be applied to your installation using the supplied rake commands. For a list of available themes run rake themes from the root of your blorgit installation. Please share any new themes you might create.
6. Comments in org-mode files Pages can optionally be opened for comments, all comments will be stored in a special * COMMENT Comments outline header appended to the end of the org file.
7. Git Synchronization By setting the git_commit configuration option to true blorgit can be made to automatically commit and push to a git repository after every comment or edit of an org-mode file.

Ruby has its own make tool called Rake. For a list of the blorgit rake commands run rake -T from the root of your blorgit installation. At the time of writing the available rake tasks are…

$ rake -T
(in /Users/eschulte/src/blorgit)
rake exported:delete  # delete all temporary exported files
rake exported:list    # list all temporary exported files
rake index            # drop a minimal index page into /Users/eschulte/Site...
rake info             # return configuration information about the current ...
rake new              # create a new blorgit instance
rake themes           # list the available themes
rake themes:default   # a default theme, should serve as a good starting point
rake themes:food      # a food theme for my recipes
rake themes:org       # an org-mode theme featuring the folding unicorn

The configuration is controlled through a YAML file located at blorgit.yml in the base of your blorgit installation. Configuration variables can be used to control the title, index page, stylesheet, the number of recent entries and directory_listings shown in the sidebar, automatic synchronization with a git repository, commentability, editability and optional password protection for posting edits, . The default configuration is…

--- 
title: Blorgit
index: index
style: stylesheet.css
recent: 5
dir_list: false
git_commit: false
commentable: true
editable: false
auth: 
- admin
- password

If you're wondering where git comes in, initialize your new blogs directory as a git repo, and post all future blogs, moderate comments and commentability of blogs, and manage configuration through git.

cd ./blogs
git init
echo ".exported_*" > .gitignore # ignore export files created automatically by blorgit
git add .
git commit -a -m "initial commit"

To change the location of the blogs directory see the blorgit.yml global configuration file in the base of your blorgit directory.

Simplicity and a small hackable code base were key goals in the construction of blorgit. The blorgit.rb file in the base of the application contains all of the logic and html. Any extensions should be possible through modification of this single file. For information on the structure of this file, or on the framework on which it is run see Sinatra.

A handy tool for hosting local sites on Mac OSX is the Apache/Passenger Pane. This allows the setup and running of local ruby web applications through a System Preferences Pane, and can be used with blorgit.

1. First follow the installation instructions from putting-the-pane-back-into-deployment.

2. clone blorgit to your ~/Sites directory

   cd ~/Sites
   git clone git://github.com/eschulte/blorgit.git
   cd blorgit
   git submodule init
   git submodule update
   

3. Create a public and tmp directory, and copy run.ru to config.ru to trick Passenger into thinking blorgit is a rails application.

   mkdir public
   mkdir tmp
   cp run.ru config.ru
   

4. rename the blorgit directory to the name of your local site (in my case "foods")

   cd ~/Sites
   mv blorgit foods
   

5. Configure blorgit as you would normally (see Getting Started (installation and use))

6. Add your new blorgit site to Passenger Pane.

   

7. Restart Apache

   sudo apachectl restart
   

8. Point your browser at the url displayed in the Passenger Pane.