So the solution to this seems to indeed be to serve the data through Flask. Each Dash app contains a Flask app, so there is no need add one only for this. I added two routes: One is serving a file from the results directory, one serves a file for a given configuration key from the config file. I have not adapted the predicted ORFs track as I was not sure how to get the correct filename. I also did not yet touch the summarize script, which can be trimmed down a lot, given that we do not need store data as base64-encoded strings anymore.
This addresses #137.
So the solution to this seems to indeed be to serve the data through Flask. Each Dash app contains a Flask app, so there is no need add one only for this. I added two routes: One is serving a file from the results directory, one serves a file for a given configuration key from the config file. I have not adapted the predicted ORFs track as I was not sure how to get the correct filename. I also did not yet touch the summarize script, which can be trimmed down a lot, given that we do not need store data as
base64
-encoded strings anymore.