Just put them in recipes. Webistrano, as I understand its workings, is
a UI that generates capfiles and invokes capistrano on them; it
doesn't reimplement the cap run itself.
FWIW I've found moving cap->web to be a good excuse to look at
re-implementing the logic to make it more data-driven than is
generally the norm for vanilla capfiles, which is possible now that
you've got the project- and stage-specific configuration variable
inheritance to call upon.
Jonathan
--
Jonathan Matthews
London, UK
http://www.jpluscplusm.com/contact.html