Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

deevus's avatar

Vapor applications may not have more than 300 public assets.

Hi there

I'm trying to migrate a Laravel app that is currently running on Forge/Envoyer to Vapor. There are a lot of assets in the public/ directory, so trying to deploy all of them gets the following error:

Vapor applications may not have more than 300 public assets.

What I don't understand about this is that the public assets end up in S3 and are served via CloudFront, so why is there a file limit? I could pull these out of the project and upload them to S3 myself, but Vapor already has this process, so it would be much better to leverage that rather than adding another thing to manage.

The only thing that I can think of is that the Vapor API itself is hosted on Lambda and that the assets artifact is sent there first before pushing to S3.

Is there a command that I don't know about for uploading to the current version's directory on S3? Or even just to get the identifier?

0 likes
1 reply
bugsysha's avatar

I would ask this question in official Vapor support channels or on twitter.

Please or to participate in this conversation.