What about tying the higher limit to a validation that the URL payload is indeed a SPARQL query? If you're really worried about abuse, you could even strip all comments and validate that the remainder is a syntactically valid SPARQL query. That would solve the main pain point of not being able to share long queries, yet not open up a pastebin for arbitrary large amounts of text.
Mar 1 2020
I have reduced the number of CPUs requested to 1, and everything is working again now.
Feb 29 2020
For what it's worth, the $HOME/.lightttpd.conf works as expected when the environment variables TEG_BACKEND_SERVICE_HOST and TEG_BACKEND_SERVICE_PORT are set. Up to now, these were set automatically from the backend deployment, so it's not a separate issue, but indeed caused by the backend failure.
Aug 17 2019
Aug 16 2019
Another example, currently has 101 results:
Aug 14 2019
Apr 17 2019
Apr 4 2019
Aug 24 2017
Merged and deployed.
Aug 9 2017
Taking this. Tracking progress in Github issue #123.