AndyButland
commented
5 months ago I think then that's the approach we'd suggest for import on your remote environment too. We're aware that particularly if you include media files, the zip files can be big and uploading via the browser can be problematic.
So you could upload the file via some other means - e.g. FTP. And then create a composer that uses the service to import from the file if found at an expected location. Obviously that's not something for day-to-day editor operations, but large imports we expect to usually be one-off operations, and this then should work OK.
Another option is to not include media files in the exported zip, making it much smaller. Transfer the files via some other means (e.g. upload to blob storage or FTP) to their expected location in your environment, and then import the zip via the UI.
We have a zip file containing the export of one of our projects. This zipfile is about 1.3 GB big.
When we try to upload this file into the new environment on live, the upload stops after about 500 MB (varies between 300 and 700MB in each try). Then without a message the upload stops and the Select ZIP file button is shown again. There is no message logged, so we cannot see what is going wrong.
When we try to upload it in a local environment the upload also stops midway but now a message is shown: No file provided for import.
We have raised the maximum upload size for files both in web.config (maxAllowedContentLength) as in appsettings.json (MaxRequestLength) to 4 GB so that can not be the problem.
Then we tried to use the ArtifactImportExportComposer.cs as found on https://docs.umbraco.com/umbraco-deploy/deployment-workflow/import-export. When we use this composer locally and put the import.zip in the right folder then the upload does work and we only get the errors for the datatypes that cannot be imported yet.
Umbraco 13.2.0 Forms 13.0.2 Deploy 13.0.4