Our portal reports backup status across multiple products. The report data is uploaded to the portal via DRF and stored in Django models.
The main object type is BaasObject, and it is associated with a Company and a backup type.
For reporting purposes, the data is rendered using Django templates. The template is available through the front-end, and is also configured to be sent as e-mail to a central e-mail address.
Improve reporting structure
The celery based scheduler currently uses management commands, but it seems to introduce a lot of redundant code. I would like to learn if there is a better way to structure the code.
Implement reporting class, if possible?
The current structure feels quite static. Ideally, I would like to introduce some code that exposes a report as an object that can be referenced by a ReportRecipients model.
11 freelancers are bidding on average €150 for this job
Hi,I am very interested in this project can u please discuss in details. we always work for client satisfaction so please initiate chat as soon as possible :) Thank you