-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce the number of files that get deployed to production. #5201
Comments
Assigning @vojtechjelinek for the first checkbox. |
Another solution that I came across is to host our own "minified" version of each dependency on a separate Github. This will ensure a constant upstream as well as control over file count. Updating the self-hosted dependency is going to be an issue. However, each dependency update is a little journey by itself so it should be treated with great care. |
At the point of writing this comment, app.yaml has a bunch of handler entries for dev mode development( Upon running production deployment, a different app.yaml (say we put it in Per Sean's recommendation:
|
(This was originally filed as #5182. Some immediate work has been done in #5196 -- thanks @vojtechjelinek! -- but there's still some more long term stuff to do, so I'm refiling.)
There is a limit of 10,000 on the number of files that can be uploaded to the production server. We have breached this limit enough times that it seems like it would be better to take active steps to control the number of files we deploy to production.
Here are some avenues for investigation:
The text was updated successfully, but these errors were encountered: