Allow specifying local file path for mbox/eml/pst #214
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added the option to specify a local file path instead of uploading a file for mbox/eml/pst ingestion. I only added the capability to the API and not on the frontend, but that could be easily added.
Seems to be working, I am still waiting after several hours to finish on my 13GB google takeout mbox file. (it seems the process is so intensive that I am basically unable to access the server even by SSH, but I can see in the hypervisor it is doing something, especially disk i/o).
Please note the code was mostly generated by AI (Claude/opencode), I also checked it roughly, although I am no typescript expert.
Here is an example API call by curl to use it (find Bearer token from some request in the browser):
Here is a precompiled version of MboxConnector.js that one could overwrite in the docker container (+restart), if someone wanted to quickly test it (v0.4.0): https://gist.github.com/mrbrdo/a5061ddbe3502820da206e6180b95f33
Related to #120