@matt well the reason I ask - and yes I acknowlege Im not being helpful by NOT answering your hosting questions - so feel free to ignore:
WF already serves statics: your css, the little client side js and the slug icons. I use this hack by mapping a folder (`/img`) out of the statics folder for images in my WF posts that end up being served from <instance>/imgs/<path+file>. Then I upload images via ftp or nfs or whatever.
Noone ever goes back and mods their old blog posts. So for old posts > <configurable time threshold> render the post as a static html page and serve it from the statics folder ($disk storage << $db) with a little bit of route map hackery to have the same URL serve up the same blog post in either static or dynamic form. Then quash that row in the db with a pointer to the static file, then garbage coll/compress the db. If you really want backwards compatibility, write encoded markdown source of the DB rows into the static html, or a
1/