@thwarted It's 21 lines and simple to use. 'rake deploy' is much better than what most WordPress users are doing to deploy an update to their theme.<p>What's the alternative? FTP? Typing the rsync command by hand each time?<p>This also assumes that you are using Sass (<a href="http://sass-lang.com/" rel="nofollow">http://sass-lang.com/</a>) and Compass (<a href="http://compass-style.org/" rel="nofollow">http://compass-style.org/</a>).<p>If you want the scoop on using Sass and Compass with WordPress check out the Compass-WordPress extension at GitHub: <a href="http://github.com/pengwynn/compass-wordpress" rel="nofollow">http://github.com/pengwynn/compass-wordpress</a><p>@smanek Capistrano is WAAAY over-kill. rsync is a better fit and --delete ensures that you delete files that don't exist on the sending side. Keeps it simple and clean.
This sure is long for running three, serially executed commands. What am I missing here? A Makefile, which is a dependency resolution DSL from before the term DSL was popular, for this is only like 6 lines, and is much terser and explicit.
Thanks, I'm currently messing with converting my (Common Lisp) webapp's CSS to SASS. This suggested it was time for me to use something a little beyond my ad-hoc conglomeration of Bash scripts I'm currently using.<p>I was actually just investigating Capistrano - but this seems so easy ...
I'm working on a Thor (<a href="http://github.com/wycats/thor" rel="nofollow">http://github.com/wycats/thor</a>) version of this as well, because I ran into the need to pass options to a task. Plus, Thor is basically writing a Ruby class.
Why not just use your favourite revision control system, e.g. svn, and push changes out using that?<p>That way you can go back in time and having a staging server if the project requires it.