You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might be a lack of understanding on my behalf (probably), but it seems odd that prepare_deployment does not resolve the full path "/vagrant/#{path}". Mysteriously, the shipped example worked for me, but my own stuff doesn't. I have renamed my apps and so on, but it all looks consistent with what you have, apart from leaving out php-related recipes and so on. Once I resolve to the full path "/vagrant/#{path}" it all works.
The text was updated successfully, but these errors were encountered:
What value were you using for deploy.{app-name}.scm.repository within your chef json? Are you saying that you tried a relative path and it didn't work until you specified an absolute path?
Any relative path should be interpreted within the context of /vagrant as the current working directory, so in the case of the example php app, dev/simple-php should resolve to /vagrant/dev/simple-php.
It might be a lack of understanding on my behalf (probably), but it seems odd that
prepare_deployment
does not resolve the full path"/vagrant/#{path}"
. Mysteriously, the shipped example worked for me, but my own stuff doesn't. I have renamed my apps and so on, but it all looks consistent with what you have, apart from leaving out php-related recipes and so on. Once I resolve to the full path"/vagrant/#{path}"
it all works.The text was updated successfully, but these errors were encountered: