Shouldn't deploy_to affect the current_path var?
I set deploy_to to /var/apps, and if I try to cap restart, it still
uses the /u/ prefix.
release_path uses the correct /var/apps prefix.
my version: 1.99.2
thanks,
Christoph
- Jamis
- Jamis
On 7/11/07, sol <ch.b...@gmail.com> wrote:
>
# some custom app vars here
Is that literally in your file, or did you elide some content before
pastie-ing it? Also, how are you testing the value of current_path?
- Jamis
On 7/11/07, sol <ch.b...@gmail.com> wrote:
>
I removed some lines where you see "# some custom app vars here" but
thats mainly usernames, password and vars for my custom tasks, like
nginx server aliases.
I don't think that this affects the path though.
Can you show me the restart task, with your changes in it?
- Jamis
On 7/11/07, sol <ch.b...@gmail.com> wrote:
>
hm, one var does:
set :mongrel_conf, "#{current_path}/config/mongrel_cluster.yml"
the others are just some strings like username, domainname, etc
> Can you show me the restart task, with your changes in it?
I meant the deploy:restart task, it uses /u/ if I try it, I did not
change anything.
also printing those vars to stdout shows the wrong path (after
deploy_to)
set(:mongrel_conf) { "#{current_path}/config/mongrel_cluster.yml" }
Putting it in braces forces it to be evaluated lazily, when it is
first needed. Which will hopefully be after you've changed the
:deploy_to variable.
- Jamis
On 7/11/07, sol <ch.b...@gmail.com> wrote:
>
Thanks a lot Jamis, although I should have noticed this myself :)