README.md in toto-0.1.2 vs README.md in toto-0.1.3

- old
+ new

@@ -17,10 +17,11 @@ how it works ------------ - content is entirely managed trough **git**; you get full fledged version control for free. - articles are stored as _.txt_ files, with embeded metadata (in yaml format). +- articles are processed through a markdown converter (rdiscount) by default. - templating is done through **ERB**. - toto is built right on top of **Rack**. - comments are handled by disqus:(http://disqus.com) - individual articles can be accessed through urls such as _/2009/11/21/blogging-with-toto_ - the archives can be accessed by year, month or day, wih the same format as above. @@ -68,17 +69,18 @@ $ git commit -m 'wrote the wizard of oz.' $ git push remote master Where `remote` is the name of your remote git repository. The article is now published. -### server +### deployment Toto is built on top of **Rack**, and hence has a **rackup** file: _config.ru_. -#### on your own +#### on your own server -You can run toto with any Rack compliant web server, such as **thin**, **mongrel** or **unicorn**. +Once you have created the remote git repo, and pushed your changes to it, you can run toto with any Rack compliant web server, +such as **thin**, **mongrel** or **unicorn**. With thin, you would do something like: $ thin start -R config.ru @@ -87,10 +89,11 @@ $ unicorn #### on heroku Toto was designed to work well with heroku:(http://heroku.com), it makes the most out of it's state-of-the-art caching, -by setting the _Cache-Control_ and _Etag_ HTTP headers. +by setting the _Cache-Control_ and _Etag_ HTTP headers. Deploying on Heroku is really easy, just get the heroku gem, +create a heroku app with `heroku create`, and push with `git push heroku master`. ### configuration You can configure toto, by modifying the _config.ru_ file. For example, if you want to set the blog author to 'John Galt', you could add `set :author, 'John Galt'` inside the `Toto::Server.new` block. Here's the options hash with the defaults: