-
Notifications
You must be signed in to change notification settings - Fork 48
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
composer_working_dir dependent on release path #37
Comments
The default set :composer_working_dir, -> { fetch(:release_path) } You can override it like this: set :composer_working_dir, -> { 'directory/with/composer/project' } Can you confirm is that works or not? I don't see how it wouldn't but you never know. |
No this does not work. My custom Here is what happens:
|
@swalkinshaw: The property "composer_project_dir" in my PR would now have the behaviour expected in your post. |
set :composer_working_dir, -> { fetch(:release_path) } You're correct that it should be: set :composer_working_dir, -> { "#{fetch(:release_path)/myDirectory}" }
# or
set :composer_working_dir, -> { File.join(fetch(:release_path), 'myDirectory') } |
If my composer project was in a subdirectory, I expect to be able to do
However this fails, since the default is dependent on
:release_path
. This dependency should probably be handled within the code. Or if I am misunderstanding the use of it, maybe a second variable for this would be useful.Never having used ruby before, I came up with this alternative:
Might be related to this: #36
The text was updated successfully, but these errors were encountered: