-
Notifications
You must be signed in to change notification settings - Fork 13
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
Unable to change git_dirconfig option #1
Comments
Thanks for the report. That should be made configurable as well. |
Yeah, I got stuck with that one too. Though configuration allows passing parameters to tar command so I got around by addin |
I have updated magedeploy2 to generate the artifacts in a |
Hi, I did check this right away, but couldn't respond earlier. Now it works as expected which is great. Just one thing, if not a problem: Regarding the artifacts_dir, it is forced to be relative path, while it would be nice to make it possible to be absolute as well. Currently if you set it to 'artifacts' it will write to '../artifacts', and be relative to 'git_dir'. Due to fact that it appends '../', it can't be set to absolute path on system. If the general idea is ok, I can make the change and create a pull request, just checking the general idea. |
Sure I don't see why this could not be a absolute path. |
In mage magedeploy2.php you can specify git_dir and app_dir to any path on disk. However, these paths are hard coded to default value of 'shop' in n98/n98-deployer package and can not be changed via configuration.
The text was updated successfully, but these errors were encountered: