Upload LFS file directly when open SERVE_DIRECT config option

[ABNER-1]

• Gitea version (or commit ref): 1.15.0+rc3
• Git version: git version 2.30.1
• Operating system: ubuntu18.04
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
• Log gist:

None

Description

The rest part of issuse #16711
Implement uploading lfs file when open SERVE_DIRECT config option.
some answers about details #16711 (comment)

[zeripath]

Docker latest isn't a version.

Do you mean 1.15.0?

[ABNER-1]

I have updated the version of gitea

[ABNER-1]

I try to add x-amz-content-sha256, and this will help us to verify the upload file is consistent with the file sha256.
(I test by editing the source code of minio rudely. If sha256 is inconsistent in signature & header & file content sha, it cause 503 error, and will not found this resource in minio.)

However, I have some questions about this.

1. Why verify action is optional?
2. If have no verify action, how can gitea know the upload phase is over and try to write a meta information?

[lunny]

Hm, should we use another config option but not still use SERVE_DIRECT?

[ABNER-1]

I can accept it.

The config doc config-cheat-sheet describe it regardless of upload or download. But splitting it to two options is ok because they both may be suitable for different situation.

However, on my opinion, the SERVE_DIRECT may be called like UPLOAD/DOWNLOAD_SERVE_DIRECT because this will make user know more clearly.