= Marley *Marley* is minimal blog engine without admin interface written in Sinatra framework (http://sinatra.rubyforge.org). It has no admin interface for writing posts. Use your favorite text editor to edit plain-text files and synchronize them to server. Marley uses plain-text files for storing articles and SQLite database for storing comments (set data location in config.yml). It comes with Rake and Capistrano tasks for deploying the application and syncing articles from your local machine to the server. The +master+ branch is bare application, +restafari_org+ branch is what runs @ www.restafari.org. (In case you like to use Marley, you should fork it and then *make your own branch* for your own styling, so you can git pull any future updates from the master and then merge/cherry-pick them into your branch. == Ingredients * Sinatra, Rack and Thin * ActiveRecord and SQLite * Akismet filtering (see ./vendor/akismetor.rb) * YAML configuration * RDiscount for Markdown --> HTML conversion * Builder for Atom feed generation * Rake and Capistrano tasks == Installation and dependencies You have to install or update following Rubygems: sudo gem install sinatra rack thin activerecord sqlite3-ruby rdiscount builder capistrano Edit this configuration file: config/config.example.yml and rename it to config.yml. Install the application with this Rake task: rake app:install Load this URL in your browser: http://localhost:4567 == Deployment on server Ensure that you have correct information in config/config.yml and then run: * cap deploy:setup * cap deploy:cold Normal Capistrano deployment procedures apply (ie. you use cap deploy very often). Of course, you have to ensure that there is at least some content on the server in data directory. See next section! == Synchronizing content Marley has no administrative interface for writing articles inside some silly </tt>. It assumes you like to write in your favorite text editor, using Markdown, previewing on the fly, and just synchronize when you're ready to publish. There are several ways how to do that: * You can be hardcore and write articles over SSH in Vim directly on the server for "just-in-time-publication" when you hit <tt>:w</tt> * You can be less glorious, of course, and save your articles to some folder on your disk and <tt>scp</tt>-ing said folder to the server. Or use SFTP? Cyberduck drag & drop? Aaargh, not reccommended unless you _really_ like to see what you're doing, in real time. * You can implement some sane practice and start versioning your writing with Git. (What else?) This way, you can setup remote repository on your server, just <tt>push</tt>-ing changes whenever you feel like you want to say something in public. A <i>post-commit hook</i> is completely neccessary in this case, of course. (It isn't paramount of convenience having to SSH on your server to run <tt>git pull origin master</tt> in some folder.) See Capistrano task <tt>cap sync:setup:hook</tt> for setting this up. * When you already use Git, you can push to Github (where else?), and have Github call Marley by it's Post-Receive Hooks (http://github.com/guides/post-receive-hooks). Github then calls Marley's <tt>/sync</tt> and it will <tt>git pull</tt> changes from Github. How is this authenticated? Good question. By setting up a (possibly long and secure) token in the config file. OMG! Could be overheard in the internets! If you're worried or prudent, do not use this. (See Capistrano task <tt>cap sync:setup:github</tt> for adding remote Github repo on the server!) You can set-up last two options by running Capistrano task <tt>cap sync:setup</tt>. Choose whether you like to upload your local data as a Git repository to the server (and setup post-receive hook in doing so) or you want to clone data from Github repository. You should add a Post-Receive URL in your repo's administration on Github as told by the task when it has runned. Of course, put other ideas in the Marley Wiki (http://github.com/karmi/marley/wikis) == Todo * Better documentation for themes (from Luke's commits) * Authenticate Github hook by HTTP-Auth, not token * Add minimal admin interface feature for filtering spam comments (based on HTTP-Auth) * Do not show spam comments in HTML and feed (after ^^^) * Enable commenters edit their comments for 15 minutes after posting (based on cookie) * Kick Markdown formatting into a Formatter so everyone can use whatever formatter she likes * Kick articles extraction logic into an Interface so everyone can use whatever data store she likes, not being plain (texter) like me == Licence Copyright (c) 2008 Karel Minarik (www.karmi.cz) Code released under the MIT license, do not reuse graphical assets and styles in the <i>restafari_org</i> branch, please