We are currently on version 9, preparing to migrate to version 10. We have a very large project with an MPR file that is currently ~250MB. We can't perform the migration to Git in our developer portal because it fails on the file size and number of commits limitations. We can probably prune our historical commits to a reasonable number, but the MPR size issue is a show stopper.
Suggested solution:
It would be a relatively simple matter to split the binary MPR into smaller chunks during the commit process. Just commit the chunked files, not the full MPR. When pulling an update, recombine the chunked files into the full MPR locally for normal Studio Pro operations.
I would think this would be a relatively easy pre- and post- action to add to the existing commit and pull process. People have been chunking large binaries into smaller parts to distribute on services like Usenet for decades.
Mendix is aware of this and are working on a solution. I forgot what is the timeline. But roughly you have a few options:
- contact mendix to get an exception for your project. This essentially skips the size check. You will probably end up with very slow project checkouts. They have tools to trim history after conversion to speed up git pulls.
- strip down your model by removing old “code” and objects. This should make your mpr smaller.
- postpone your git conversion until mendix releases studio pro with the mpr file split up into smaller ones. This is already on the roadmap. (Kinda your suggestion except this is built into studio pro)
-