News for hackers. Stuff that matters.

A comment on PHP in 2019. Parent comment

Re:PHP in 2019 by Intermernet on Wednesday May 15, 2019 @06:29AM (#19918020)
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?
[ Parent | on HN ]
Re:PHP in 2019 by bayesian_horse on Wednesday May 15, 2019 @07:08AM (#19918221)
Composer is very useful in penetration testing. Lot's of good information in the composer.json files people keep forgetting to block..
[ Parent | on HN ]
Re:PHP in 2019 by ceejayoz on Wednesday May 15, 2019 @07:23AM (#19918307)
A 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.
[ Parent | on HN ]
Re:PHP in 2019 by bashy on Wednesday May 15, 2019 @06:30AM (#19918025)
Yeah I remember the problems with composer. It's good now.
[ Parent | on HN ]
Re:PHP in 2019 by codedokode on Wednesday May 15, 2019 @06:14PM (#19924308)
It is not a leak, it just loads too much data into memory so you need about 1 Gb of RAM to run composer update.
[ Parent | on HN ]
Re:PHP in 2019 by jbrooksuk on Wednesday May 15, 2019 @06:33AM (#19918039)
Yeah, that's not a thing anymore.
[ Parent | on HN ]