I'm using lighttpd to map Tonido to a path among my existing lighttpd-served pages. Why would I do this? There are a few reasons. You might want to run several instances of Tonido on a multiple-user system, with each user having appropriate permissions when browsing files, you might want to use Tonido with existing SSL credentials already served by lighttpd, or you might just want it integrated into your existing site. Here's the recipe I'm using with v1.5 (svn), using mod_proxy_core and mod_proxy_backend_http:

The (/?|/.*) is important so that it will catch /tonido/unhelpful as well as paths under it. The rewrite-response part is important also, since Tonido will respond with a redirect to /ui/core/index.html when you try to access /, and we want that rewritten to be under the /tonido/<USER> directory. If there's only one instance of Tonido, you could leave out the <USER> subdirectory to just serve it as /tonido. For multiple instances you'd write several such rules with a different <USER> for each.

edit: use a look-behind to make it a bit more robust - should catch any redirects that don't have the /tonido/<USER> prefix now.