-
Notifications
You must be signed in to change notification settings - Fork 447
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
Server size too big #15
Comments
There are a couple causes I can think of off the top of my head.
Have you tried any other services besides cyclic and vercel? I've heard that render is a good alternative. If it is still too big, I would try downloading polaris as a zip file and then uploading the unzipped contents to a new repo. This should remove all commit history making the repo much smaller. We are also planning to move most of the images to our assets repo, which will also help with the size issue. |
Render doesn't allow proxies, and zipping it is still to large |
Have you tried removing commit history? |
How? |
Download polaris as a zip file and then upload the unzipped contents to a new repo and try to deploy that. |
Did that, still too large |
Repo is here: https://github.com/EnchantedDonutStudioz/VeryGoodProxy |
Is there a way to not exceed the server size on vercel without unzipping most files? |
I'd assume they'd have safeguards to prevent that. |
Most of the size is from the images folder. We're working on moving the images to our assets repo. |
We have migrated all of our images over to the assets repo. This should fix the size issue. |
It is still way too big |
The deployment size issue has been fixed. Vercel still does not support Polaris, though we're working on a version of Polaris that will be deployable to most hosting providers. Including vercel. |
Unable to deploy project because server size is too big and won't deploy
The text was updated successfully, but these errors were encountered: