The way the current backend code handles the file new documents being saved is to store the file on a temporary location within the server, then asynchronously parse the file to extract it's text and save it to the document database, then finally the actual file is moved to another location with an unique name to be downloaded by the user when requested.
For the dev environment, the backend code is currently hosted at Heroku.
Two problems stem from this:
- Heroku is not supposed to serve as file storage, so the second part - moving to another location in the server to serve as cold storage for the file - just won't work.
- I'm not sure if it's possible to spin up new threads on the free tier dyno for the async processing of the file like we do right now.
The way the current backend code handles the file new documents being saved is to store the file on a temporary location within the server, then asynchronously parse the file to extract it's text and save it to the document database, then finally the actual file is moved to another location with an unique name to be downloaded by the user when requested.
For the dev environment, the backend code is currently hosted at Heroku.
Two problems stem from this: