Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prepare_deployments #10

Closed
felixSchl opened this issue Nov 6, 2015 · 2 comments
Closed

prepare_deployments #10

felixSchl opened this issue Nov 6, 2015 · 2 comments

Comments

@felixSchl
Copy link

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.

@mikegreiling
Copy link
Member

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?

@mikegreiling
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants