$CAPISTRANO:HOST$ is not a variable; it simply gets gsubbed with the
value of the current server name immediately before the command is
handed off to the server. It will not be affected by caching.
Caching only applies to variables set with a block, e.g.
set(:releases) { capture("ls -xt #{releases_dir}").split }
- Jamis
On 2/13/09 9:38 AM, Gerhardus Geldenhuis wrote:
> Hi
> is any "caching" that capistrano does only for the duration of a
> running cap command?
>
> I have seen some weird errors which I thought might potentially
> caching related.
>
> Basically I thing this variable was not being set $CAPISTRANO:HOST$
> properly which caused some of the tasks to not work correctly...
>
> Is there a way to control/clear caching?
>
> Regards
> >
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
