Maverick 1.2 has regressed slightly in that there is no web mavlink related services (will come in 1.3), and we are deprecating maverick-web-legacy (https://github.com/goodrobots/maverick/issues/955), so this facility needs to be re-implemented for 1.3 by -api and -web. -api should take care of somehow receiving log files and extracting to timeseries database, and -web should provide the frontend to this action.
Actually this doesn't have to be serviced by -api. This could continue to be a standalone microservice just served up by nginx, with a -web frontend, at least for the near future.
https://github.com/goodrobots/maverick-web-legacy/blob/master/tornado/file_upload.py is used to upload dataflash logs to mavlogd, which extracts the data and inserts into influxdb timeseries database.
Maverick 1.2 has regressed slightly in that there is no web mavlink related services (will come in 1.3), and we are deprecating maverick-web-legacy (https://github.com/goodrobots/maverick/issues/955), so this facility needs to be re-implemented for 1.3 by -api and -web. -api should take care of somehow receiving log files and extracting to timeseries database, and -web should provide the frontend to this action.