introduce FASTCGI_READ_TIMEOUT #442
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes: #58
I want to make
fastcgi_read_timeoutin Nginx configurable, so the user can set another value to prevent connection timeouts between Nginx and PHP.background: I tried Wallabag and started to use the import function with a 1400 bookmark Json file from Firefox. What I've read so far, Wallabag was never build and tested for that use case, unfortunatelly I have it. With increase the timeout in Nginx and the Memory limit in PHP it works at the end.
Wallabag is running on Kubernetes cluster, the Ingress has proxy timeout parameter set. The web page returns Error 500 after a while, but when you follow the prod.log Wallabag proceed the bookmarks further in the background. Great!