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

Composer Cache #18

Open
Toflar opened this issue Jul 6, 2016 · 2 comments
Open

Composer Cache #18

Toflar opened this issue Jul 6, 2016 · 2 comments
Labels

Comments

@Toflar
Copy link
Contributor

Toflar commented Jul 6, 2016

The Composer cache should probably live within the tenside directory, otherwise it might conflict with a cache directory of an arbitrary project.

@discordier
Copy link
Member

Well, it is the cache, the cache should be the same across ALL installations for maximum benefit.

In the end, you most likely do not want to download the same package list over and over again when updating multiple installations let alone download the zip files etc. more than once.

I have many installations at my place and they all share the same cache folder in my user home and therefore speeding up installations.

I wonder why there should arise conflicts. Can you please elaborate on problems you experienced?

@Toflar
Copy link
Contributor Author

Toflar commented Jul 11, 2016

screen shot 2016-07-11 at 10 36 44
This is what happens. See the cache folder on top level? What if the application you execute a create-project from already has a cache folder on top level? Imho the cache folder of composer should go to the tenside folder because Tenside manages it.

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

No branches or pull requests

2 participants