5 ms·
Last time I used composer (about 3 years ago) it had a nasty memory leak that eventually meant I had to run the build on a higher specced instance than the actu
by Intermernet 7y ago
Last time I used composer (about 3 years ago) it had a nasty memory leak that eventually meant I had to run the build on a higher specced instance than the actual application. This was mainly due to the ridiculous dependancies of the application, but it was almost a show stopper. Has this improved?
- bashy 7y agoYeah I remember the problems with composer. It's good now.
- jbrooksuk 7y agoYeah, that's not a thing anymore.
- bayesian_horse 7y agoComposer is very useful in penetration testing. Lot's of good information in the composer.json files people keep forgetting to block..
- ceejayoz 7y agoA Laravel or Symfony app operates out of the public/ directory, so composer.json shouldn’t need any blocking typically - it’d be outside the web root.
- codedokode 7y agoIt is not a leak, it just loads too much data into memory so you need about 1 Gb of RAM to run composer update.