Batch import allows, for example, to upload crash reports to a web server using some external script, copy the uploaded files to another machine over SSH and import the files to the CrashFix server installed on that machine. Using this way, you can install CrashFix on a machine inside of local area network (LAN) and not expose its web interface to outside world, thus storing your files in a more secure way.
DOCUMENT_ROOT/crashfix/protected/import/crashReports project1 version1 crashreport1.zip crashreport2.zip ... version2 crashreport3.zip crashreport4.zip ... ... project2 version3 crashreport5.zip crashreport6.zip ... version4 crashreport7.zip crashreport8.zip ... ... ...
The subdirectory structure presented above is required to correctly determine crash report's project name and version.
DOCUMENT_ROOT/crashfix/protected/import/debugInfo project1 version1 symbol1.pdb symbol2.pdb symbol3.pdb ... ... project2 version2 symbol4.pdb symbol5.pdb symbol6.pdb ... ... ...
The subdirectory structure presented above is required to correctly determine symbol file's project name.
Since v.1.0.2, it is possible to tell CrashFix to temporarily stop batch import of crash reports and debug info files by placing the importlock file to the DOCUMENT_ROOT/crashfix/protected/import directory. If CrashFix encounters that file, it suspends the batch import operation. Removing the file would allow CrashFix to resume the batch import operation.