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

Unable to change git_dirconfig option #1

Open
udovicic opened this issue Mar 5, 2017 · 5 comments
Open

Unable to change git_dirconfig option #1

udovicic opened this issue Mar 5, 2017 · 5 comments

Comments

@udovicic
Copy link

udovicic commented Mar 5, 2017

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.

@mwr
Copy link
Owner

mwr commented Mar 5, 2017

Thanks for the report. That should be made configurable as well.
I guess we need to generate the tar.gz files to a location outside of the git_dir dir as well. Otherwise there might be an endless loop whilst creating the shop package.
I'll update that in time.

@udovicic
Copy link
Author

udovicic commented Mar 5, 2017

Yeah, I got stuck with that one too. Though configuration allows passing parameters to tar command so I got around by addin '--exclude=\'*.tar.gz\'', to options of final .tar.gz. But this is kind of a hack around, it would be much nicer to have them outside the repo dir in the first place.

@mwr
Copy link
Owner

mwr commented Mar 6, 2017

I have updated magedeploy2 to generate the artifacts in a artifacts_dir.
Furthermore the deployer scripts now also use an artifacts_dir where they get the packages from.
So it should no longer be necessary to use --exclude.

@udovicic
Copy link
Author

udovicic commented Mar 9, 2017

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.

@mwr
Copy link
Owner

mwr commented Mar 9, 2017

Sure I don't see why this could not be a absolute path.
I am always happy about a pull request.

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