aboutsummaryrefslogtreecommitdiffstats
path: root/cmd/git-lfs-server/main.go
Commit message (Collapse)AuthorAgeFilesLines
* Better logging (for a standalone server)Libravatar Rutger Broekhoff2024-01-021-7/+6
|
* 🚫 No CGI 🚫Libravatar Rutger Broekhoff2024-01-021-2/+10
|
* catch panicLibravatar Rutger Broekhoff2024-01-021-1/+10
|
* Try generating more descriptive errorsLibravatar Rutger Broekhoff2024-01-021-1/+10
|
* lol oopsLibravatar Rutger Broekhoff2024-01-021-1/+1
|
* Uploading objects is a PUT, not a POSTLibravatar Rutger Broekhoff2024-01-021-1/+1
|
* Fix upload regexLibravatar Rutger Broekhoff2024-01-021-1/+1
|
* Upload validation by proxyingLibravatar Rutger Broekhoff2024-01-021-58/+263
| | | | Yes, the code is a mess
* Specify x-amz-content-sha256 as in Scaleway docsLibravatar Rutger Broekhoff2023-12-311-0/+1
|
* Try formatting x-amz-checksum-sha256 as Base64Libravatar Rutger Broekhoff2023-12-311-1/+15
| | | | | | | Although this already looks like a lost cause (Scaleway Object Storage doesn't seem to care about these headers -- certainly not about Content-Length -- I wanted to see if I could still get automatic checksum verification working.
* Fix mistakeLibravatar Rutger Broekhoff2023-12-301-4/+4
|
* Only print environment when dyingLibravatar Rutger Broekhoff2023-12-301-5/+4
|
* Implement authorization in git-lfs-server, test presigned PUTsLibravatar Rutger Broekhoff2023-12-301-29/+177
|
* Implement git-lfs-authenticateLibravatar Rutger Broekhoff2023-12-301-25/+7
|
* URL as string, lesson learnedLibravatar Rutger Broekhoff2023-12-301-2/+2
|
* Repo .git suffixLibravatar Rutger Broekhoff2023-12-301-1/+1
|
* Request IDs!Libravatar Rutger Broekhoff2023-12-301-20/+40
|
* Allow setting Gitolite binary path via envLibravatar Rutger Broekhoff2023-12-291-8/+14
|
* Log moreLibravatar Rutger Broekhoff2023-12-291-0/+3
|
* Swap strings.TrimPrefix argsLibravatar Rutger Broekhoff2023-12-291-2/+2
|
* Log reqPath 2x moreLibravatar Rutger Broekhoff2023-12-291-0/+2
|
* SubmatchLibravatar Rutger Broekhoff2023-12-291-5/+7
|
* Prefer PATH_INFO over request URLLibravatar Rutger Broekhoff2023-12-291-1/+5
|
* List envs at startLibravatar Rutger Broekhoff2023-12-291-11/+21
|
* Improve handling of MIME typesLibravatar Rutger Broekhoff2023-12-291-5/+17
|
* Read S3 secrets from fileLibravatar Rutger Broekhoff2023-12-291-13/+23
|
* Add 'lfs/objects' part to pathLibravatar Rutger Broekhoff2023-12-291-1/+1
|
* Write basic read-only public Git LFS serverLibravatar Rutger Broekhoff2023-12-291-0/+329
| | | | | | | | | | | | | | | | | | | | | | | | | | The 'integration' with Gitolite is honestly pretty bad and should not be taken very seriously: it runs the 'gitolite access' command to check if some user (e.g., daemon/nobody) should be able to read from the repository. Based on this, it grants access to objects stored in S3, by generating Presigned GetObject URLs using the S3 API. Of course, this integration with Gitolite (especially when using the daemon user to check if the user should be able to read) is not very 'high-value': 1. If we already make use of the daemon pseudo-user to control access to public repositories, we may as well check for the existence of git-daemon-export-ok files. In case they exist, we simply assume that the repository is meant to be shown on the public internet and that therefore the LFS archive should also be considered 'open to the public'. 2. The way that Gitolite commands are currently run, this program breaks when not running under the git user without extra configuration; Gitolite decides where repositories are based on the HOME environment variable. This program currently does not set this. This could be set by the CGI server (or fcgiwrap) and would unbreak the system. There's no support for any more advanced kind of authn/authz. Uploading is also not supported yet. That's still to come.
* Initial commitLibravatar Rutger Broekhoff2023-12-291-0/+1
generated by cgit v1.2.3 (git 2.45.2) at 2024-11-18 22:49:03 +0000