> I don't want to bother with hosting a dynamic website that I would have to manage.

Out of curiosity, after once deploying it, what're some responsibilities that entail from hosting a dynamic website vs. a static one? Isn't it basically a matter of writing (/copying a good one and retrofitting) a fabric script, perhaps doing just a few things with some Apache/nginx config files, and just putting it up? What exactly makes it more hands-on post-launch?

I had been under the impression that this process would not take more than a few hours by itself.