Re:How to Keep WordPress Secure
by idlewords on Sunday September 06, 2009 @04:14AM
(#807601)
An approach I really like is to run your blog software of choice locally, then rsync the generated flat files to a server. If you want comments, you'll need to maintain some dynamic component on the server, but it still massively reduces your exposure.
[ Parent
| on HN ]
Re:How to Keep WordPress Secure
by tlrobinson on Sunday September 06, 2009 @06:15AM
(#807665)
I've started using Jekyll + Disqus for simple things (see http://narwhaljs.org for an example).
Much less hassle than setting up a database, installing Wordpress (as easy as it is) and most of all remembering to update Wordpress every few weeks, as long as you don't need in-browser editing and such.
With Github pages (http://github.com/blog/272-github-pages) it's as simple as pushing your source templates and documents (in HTML, Markdown, or Textile)
Jekyll is a little limited though, so I also have some scripts that do a little preprocessing before handing it off to Jekyll.
Movable Type takes this approach, even with comments.
Source: http://www.codinghorror.com/blog/archives/001291.html