The following MR's have been submitted:
A number of fixes:
Add Summon() hook/handler
Fix process management count
a) Delay adding a new queueworker process slightly to make sure database is updated (avoid race)
b) Add processes dynamically until max process count is reached (previously, the queueworker would prevent new processes if there were too many, but it wouldn't add processes if there was a lot of work to do. Now, as long as there is work to do, the queueworker will kick off new processes until the maximum number of workers is reached)
With these updates, I think we are very much approaching a stable working queueworker. This version has been stress tested using a mass-photo import tool that imports photos from a ZIP archive. With the new Summon() hook and the more robust process count management, things run consistently and reliably and avoid system crashes and fires off the background processes without timing out. Basically, things can be completely DUMPED into the queue rapidly without any need for internal timeouts in front-end processes which would be required otherwise.
This should be helpful for other tools such as content importing and copying files/data from other sites which can suffer from web server timeout issues.
SERVE STATIC FILES https://framagit.org/hubzilla/core/merge_requests/1692
if the query variable q= is fed the location of a file with the following extensions and that file exists, serve it directly from the file system:
In most cases, the web server should be configured to intercept these files and a request should never actually get to us. In some specialized circumstances, there may be a need to have the application handle these files.
Note: Because they are static files, they are set to allow caching under the same terms as the published web server configuration recommendations.
!!zotlabs.org | Hubzilla Development