Serve SAO custom files directly from trytond routes
These files could be served by reading them from a path configured in the configuration.
- It would avoid 405 requests from the browser when they do not exist.
- Avoid adding files to the SAO source in deployments.
- As an addition (or idea), you could also read
.js
and.css
files from each module and serve them dynamically.