Level 67
@nolannordlund You should check out the Laravel YouTube channel series about Vapor. Somewhere in there they talk about size limits for artifacts and how to get around that with Docker containers.
1 like
Feb 26, 2021
4
Level 4
Vapor deployment size is too big
I'm running into the deployment size limit with one of my Vapor projects. I've been deploying apps on Vapor for a while and this is the first time I've had this issue. My first thought was to try separate-vendor: true on my environment but the deployment artifact is the same size causing the deployment to fail still. Is separate-vendor still a thing? I know I had seen it in the past but I don't actually see it in the docs anymore. I don't have many public assets either so I'm not really sure why the deployment artifact is so big suddenly. I could also go the docker route if needed but I feel like docker has always been more trouble than it is worth.
Level 10
I've hitted the same problem as @nolannordlund and not looking forward to go for the docker way.
What is counted into the "Deployment Artifact"? I am trying to figure out what has been the reason that it has gone such big.
Level 3
You may want to check your storage->framework->cache for large hidden cache files. I ran into this issue when laravel-excel created a bunch of huge cache files locally that I wasn't clearing out before I deployed.
Level 67
Docker based runtimes allow you to package and deploy applications up to 10GB in size
https://docs.vapor.build/1.0/projects/environments.html#runtime
1 like
Please or to participate in this conversation.