support streaming content from S3, start using it in the webserver #2849
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.
First step of streaming support for content. Adds streaming support to our storage backends (only for testing in the db backend, so no real streaming there). Then uses axum's streaming response feature to stream the responses to the client.
Idea is also to give up size limits since we don't have memory issues any more.
Next steps after this:
My guess is that all content rendered via askama can't really be streamed, perhaps I switch to a manual streaming impl for bigger streamable things like the sitemap endpoints.