It's a lot easier to just 'scp ~/blog/. new-server:/var/www' than to set up a database server, go trough configuration and hardening of apache and php (or whatever) and make everything play together, again.
Well, you need to do some configuration and hardening no matter what. And while I don't use PHP anymore, I've found that for what I do the deployment story these days is easy enough.
Some friends of mine and I are planning a hosted service for this, where users can push sites trough git, scp, ftp or interactively maintain the site trough a panel (using JavaScript) - and download the entire site at any time as a zipfile (or git clone). The sites will be static, but there will be (optional) comments, using a 3rd party service.
So after suggesting people don't trust third-party services, you're going to start and advertise your own, and integrate someone else's service into it? :)
Well, you need to do some configuration and hardening no matter what. And while I don't use PHP anymore, I've found that for what I do the deployment story these days is easy enough.
Some friends of mine and I are planning a hosted service for this, where users can push sites trough git, scp, ftp or interactively maintain the site trough a panel (using JavaScript) - and download the entire site at any time as a zipfile (or git clone). The sites will be static, but there will be (optional) comments, using a 3rd party service.
So after suggesting people don't trust third-party services, you're going to start and advertise your own, and integrate someone else's service into it? :)