Skip to content

Latest commit

 

History

History
107 lines (84 loc) · 3.92 KB

blorgit.org

File metadata and controls

107 lines (84 loc) · 3.92 KB
Raw

blorgit (blog powered by org-mode and git)

design

Thinking of using sinatra for the framework, active_file for object persistence, and acts_as_org for the org-mode exportation/interaction.

The overriding goal will be simplicity.

notes

sinatra

Sinatra is a very nice little mini-framework or DSL for writing simple single-file web applications.

specific issues

send_data

http://sinatra.lighthouseapp.com/projects/9779/tickets/143-send_data-no-longer-present

running under a url prefix

deployment with capistrano and nginx

tasks [11/11]

setup dir listing

setup a global object with title/description etc.

this lives in the root of the blogs directory at .blorgit.yml

directory local blorgit config

  • State “DONE” from “TODO” [2009-05-02 Sat 12:55]
  • State “TODO” from “” [2009-04-09 Thu 13:32]
Rather than one global blorgit config file, try searching down through the directories, so that more precise site-configs can be used.

save hook (for commits to git)

  • State “DONE” from “TODO” [2009-05-02 Sat 12:39]
  • State “TODO” from “” [2009-04-09 Thu 13:31]
add a after-save hook for when a blog is saved.

then use this to implement a simple git commit

The following will push on every commit

echo 'git push' > .git/hooks/post-commit

setup dir listing

setup a global object with title/description etc.

this lives in the root of the blogs directory at .blorgit.yml

directory local blorgit config

  • State “DONE” from “TODO” [2009-05-02 Sat 10:29]
  • State “TODO” from “” [2009-04-09 Thu 13:32]
Rather than one global blorgit config file, try searching down through the directories, so that more precise site-configs can be used.

set org-mode content type correctly

  • State “DONE” from “TODO” [2009-05-14 Thu 06:17]
  • State “TODO” from “” [2009-05-13 Wed 20:31]
something along these lines will help rewriting-content-types-with-rack

implemented in rewrite_content_disposition.rb

MAYBE users

should be read from a yaml file in the blogs directory (allowing maintenance through git/VC)

would require some form of password hashing (add a ‘signup’ form which users can use to add themselves to the users yaml file, then admin must set a “activated” field to true)

once this is in place it should be used for comments, and for git commits.

might be easy to use openID

MAYBE optionally read sidebar/title info from template files

MAYBE add support for ruby 1.9

  • State “TODO” from “” [2009-04-02 Thu 06:22]

after a fresh install on debian with ruby1.9, note works with ruby1.8

(in /home/eschulte/src/blorgit)
rake aborted!
uninitialized constant URI::Parser
/home/eschulte/src/blorgit/Rakefile:1:in `require'
(See full trace by running task with --trace)

dict

LocalWords: sinatra faq