Serve trac static files as static resources (not involving python)

[strk]

See ​https://trac.edgewall.org/wiki/TracInstall#MappingStaticResources

[strk]

I've deployed serving static files without using python on the staging server and after testing I'm deploying to production.

See the ansible part here: ​https://git.osgeo.org/gitea/sac/ansible-deployment/commit/b7eb20f11552aba3b4a82561ab9a14d61f0d00de

There is a non-ansible part which was done manually before the deploy and is now documented in ​https://wiki.osgeo.org/wiki/Trac#Static_files_deploy

I guess we could make an ansible task for that as well, which should only run when trac is upgraded or a new plugin is installed.

[strk]

Serving static files like this seem to also help with the 502 ( bad gateway ) responses ticketed in #3271

[strk]

Closing as completed

[strk]

For the record, now Ansible does the deploy too: ​https://git.osgeo.org/gitea/sac/ansible-deployment/commit/8a7dbe136f13edcc6aa8b02df2ab56a861ec135a

[strk]

And we do use the same url for common assets of every trac environment too now, with ​https://git.osgeo.org/gitea/sac/ansible-deployment/commit/741a6f2e41c54e808bbaf25b673bec9f0507cbb6

AND with droppign the local override of htdocs_location in each env's trac.ini

[strk]

Reopening as it's happening again. It may be a segfault of apache.