toto – git powered blog engine

Just came across toto [http://github.com/cloudhead/toto], a minimalistic git powered blog engine. Using git as the datasource for you blog engine is a really great idea since all of you posts will be Version Controlled using git, and you can use github.com if you don’t have access to a git repository.

Qouting the REAME from toto

philosophy

Everything that can be done better with another tool should be, but one should not have too much pie to stay fit. In other words, toto does away with web frameworks or DSLs such as sinatra, and is built right on top of rack. There is no database or ORM either, we use plain text files.

Toto was designed to be used with a reverse-proxy cache, such as Varnish. This makes it an ideal candidate for heroku.

Oh, and everything that can be done with git, is.

If you think about it, a VCS (git, hg, svn, etc) makes for a great datasource for many other application, all you need is a repository and your application now has built in version control. Also, you eliminate the need to have a full blown DB to power your application. Got a few projects were I could apply this to.

Still not sure if I want to keep WordPress or roll my own (using django). Any suggestions?

No related posts.

  • powered by blogengine platform help me earn more profits.
  • We're using toto to power our blog. Check it out:

    http://www.stickermule.com/blog

    One of the coolest aspects about toto is how easy it is to manage the metadata about your post. If I want to change the author name or, if I'm posting for someone else, I just change the author tag. We also liked it because it was easy to integrate into our overall site design. Plus we get to run totally on heroku.
  • blogengine 1.6 really great than the older one. From wordpress to blogengine
  • I prefer to use wordpress than blogengine because wordpress is easy to use and lots of plugins to be used. And most blogger prefer to use wordpress than others. http://toppedia.com/mma-pound-for-pound/
blog comments powered by Disqus