- Newest
- Most votes
- Most comments
For future reference, I figured this out as follows.
I had been getting "No composer.json file detected" in my logs.
I discovered that because of the way I was zipping my package on macOS (using the native right click > Compress), it puts the files in a sub-folder inside the zipped package. So the composer.json was not at the "root" level of my package. I added it to the "root" level, and then once deployed I got the following in the logs:
Found composer.json file. Attempting to install vendors. (...)
And then the path to "vendor/autoload.php" was not in the directory with my application either (NOT /var/app/current/application-files/web/vendor), but closer to the root level (e.g. /var/app/current/vendor)
Hopefully this saves someone else some headaches!
Relevant content
- asked 3 years ago
- asked 3 years ago
- Accepted Answerasked 4 months ago
- asked a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago