Nicholas, is that for your own use? In which case I'd wager a "hacky" way to post is fine (as opposed to a web interface + rich editing).
For a recent project I created a post via capistrano thing that worked really well. I'd create a directory with a text file in it (first line becomes the post title, the remaining becomes the body), a folder inside called "photos" means the photos you wanna upload along with the post, then go $ cap mytaskfoo DIR=path/to/post_dir uploads post_dir to the server, runs a rake task to pick it up, and voi'la. http://github.com/juliocesar/3weeksinbrazil/blob/7784cabeed0781989790f1f104b1a0c5bf9c8715/Capfile Alternatively, have a look at http://github.com/kubicek/marley/tree/master. I unfortunately found out about it too late, otherwise I'd have gone for it. On Wed, Jul 1, 2009 at 2:09 PM, Tim Lucas<[email protected]> wrote: > > On 01/07/2009, at 1:36 PM, Dr Nic Williams wrote: > >> I am intrigued by Tim Lucas's CMS-by-Github approach. It was sweet. > > ...which was: give them access to github and let them edit haml files > directly via the github web interface. Git pull redeploy the site (or > just the markdown files) on post-commit or via a URL. > > This is really only good for editing bits of existing content, not for > creating lots of new content. > > -- tim > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~----------~----~----~----~------~----~------~--~---
