beat.web is not django-friendly
The static files and templates used by each beat.web subapplications (e.g. beat.web.algorithms) are not stored inside the subapplication, but in a central location inside the package.
The end result is that the location of templates and static files needs to be configured by hand every time a deployment is performed. This is particularly important if for example the django version is updated or if an external django application is added to the platform.
To fix this issue, we need to:
[x] package static files and templates belonging to each subapplication within the subapplication directory.
[x] update the
development and production settings.py to reflect this modifications.
[x] use routinely
django collectstatic to collect all static files that require serving through a dedicated URL.