diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-27 09:06:40 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-27 09:06:40 +0300 |
| commit | 688e33953d34ab8cd348d02ce79d8fdfe5353a03 (patch) | |
| tree | ee102361fc8a5bf5b2f4b05ca79ccef27b5c3102 /doc/development/packages.md | |
| parent | 91f027ede40879af0bce406f2872e8d35c01e334 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/packages.md')
| -rw-r--r-- | doc/development/packages.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/development/packages.md b/doc/development/packages.md index 30f22c13525..951a8f2b346 100644 --- a/doc/development/packages.md +++ b/doc/development/packages.md @@ -90,14 +90,14 @@ model for that package type. ## File uploads -File uploads should be handled by GitLab workhorse using object accelerated uploads. What this means is that +File uploads should be handled by GitLab Workhorse using object accelerated uploads. What this means is that the workhorse proxy that checks all incoming requests to GitLab will intercept the upload request, upload the file, and forward a request to the main GitLab codebase only containing the metadata and file location rather than the file itself. An overview of this process can be found in the [development documentation](uploads.md#workhorse-object-storage-acceleration). In terms of code, this means a route will need to be added to the -[gitlab-workhorse project](https://gitlab.com/gitlab-org/gitlab-workhorse) for each level of remote being added +[GitLab Workhorse project](https://gitlab.com/gitlab-org/gitlab-workhorse) for each level of remote being added (instance, group, project). [This merge request](https://gitlab.com/gitlab-org/gitlab-workhorse/merge_requests/412/diffs) demonstrates adding an instance-level endpoint for Conan to workhorse. You can also see the Maven project level endpoint implemented in the same file. @@ -164,7 +164,7 @@ process. These changes represent all that is needed to deliver a minimally usable package management system. -1. Empty file structure (api file, base service for this package) +1. Empty file structure (API file, base service for this package) 1. Authentication system for 'logging in' to the package manager 1. Identify metadata and create applicable tables 1. Workhorse route for [object storage accelerated uploads](uploads.md#workhorse-object-storage-acceleration) |