Also, there's this webapp called http://droppages.com/ which makes publishing from DropBox even easier.
Though personally, if I had to help a non-technical friend with setting up a blog, I'd just send him to Wordpress.com.
It's actually a really kickass feature
I suspect it's easier to go to a new client and set up dropbox on it and link it in, than it is to set up rsync and any necessary keys or firewall holes or if you are using windows, the cygwin system to support rsync.
There's a lot to be said about simplicity and ubiquity, especially if it's to encourage making a blog post, and not discourage it.
That said, using dropbox for this is terribly problematic in terms of security.
In addition, as I'm sure you recognize, this reduces breaking into your hardened box and filling it with unicorn pr0n to swiping your friend's laptop while she is in the loo at the Starbucks.
So someone can steal the key to your server with a few minutes access to your home computers or laptops and you will not know until you have unicorn pron all over your blog.
This may be fine, and I mean that, for a personal blog (that also has regular backups.) I wouldn't set this up for clients (as suggested by others) to make it easier for them to blog, I think I would find a different solution for them.
Don't get me wrong. For my own personal needs, I think your solution is better than say, posterous which seems to be going downhill fast.
I like the idea of easily, quickly, blogging within emacs.
Is there a reason this wouldn't work for your use case?
I've been very happily running it on my headless web server for over a year. There's a CLI installer, and you can do things using the 'dropbox' command-line utility.
And compile markdown files to static HTML to be served directly on the target machine.
build/project_min.js: build/project.js
rm -f $@
curl -s --data-urlencode 'js_code@build/project.js' --data-urlencode 'output_format=text' --data-urlencode 'output_info=compiled_code' http://closure-compiler.appspot.com/compile >> $@
h/t @enaeseth, edited for formattingThey're all already too busy frying the pranes.
Seriously though, a Makefile in your web directory with a default target that rsyncs your content up to your webserver via ssh solves this problem much more elegantly, without relying on a third party service. Bonus points for you if you render/minify your sass/scss and/or coffeescript as a target dependency.
PS: Put your remote username and remote port (if custom) for a given host in your ~/.ssh/config file, along with any necessary 'ProxyCommand's to allow direct "rsync ./ $hostname:public_html/" or such in your makefile.