# GitLab subscription
> 原文:[https://docs.gitlab.com/ee/subscriptions/](https://docs.gitlab.com/ee/subscriptions/)
* [Choosing a GitLab subscription](#choosing-a-gitlab-subscription)
* [Choosing a GitLab tier](#choosing-a-gitlab-tier)
* [Choosing between GitLab.com or self-managed](#choosing-between-gitlabcom-or-self-managed)
* [Choosing a GitLab.com group or personal subscription](#choosing-a-gitlabcom-group-or-personal-subscription)
* [Choosing the number of users](#choosing-the-number-of-users)
* [GitLab.com](#gitlabcom)
* [Self-managed](#self-managed)
* [Users statistics](#users-statistics)
* [Obtain a GitLab subscription](#obtain-a-gitlab-subscription)
* [Subscribe to GitLab.com](#subscribe-to-gitlabcom)
* [Subscribe through GitLab self-managed](#subscribe-through-gitlab-self-managed)
* [Manage your GitLab account](#manage-your-gitlab-account)
* [Change billing information](#change-billing-information)
* [Change payment method](#change-payment-method)
* [Change the linked account](#change-the-linked-account)
* [Change the associated namespace](#change-the-associated-namespace)
* [Change customer portal account password](#change-customer-portal-account-password)
* [View your subscription](#view-your-subscription)
* [View your GitLab.com subscription](#view-your-gitlabcom-subscription)
* [View your self-managed subscription](#view-your-self-managed-subscription)
* [Renew your subscription](#renew-your-subscription)
* [Prepare for renewal by reviewing your account](#prepare-for-renewal-by-reviewing-your-account)
* [Users over License](#users-over-license)
* [Purchase additional seats for GitLab.com](#purchase-additional-seats-for-gitlabcom)
* [Purchase additional users for self-managed](#purchase-additional-users-for-self-managed)
* [Seat Link](#seat-link)
* [Disable Seat Link](#disable-seat-link)
* [Renew or change a GitLab.com subscription](#renew-or-change-a-gitlabcom-subscription)
* [Automatic renewal](#automatic-renewal)
* [Renew a self-managed subscription](#renew-a-self-managed-subscription)
* [Upgrade your subscription tier](#upgrade-your-subscription-tier)
* [Upgrade your GitLab.com subscription tier](#upgrade-your-gitlabcom-subscription-tier)
* [Upgrade your self-managed subscription tier](#upgrade-your-self-managed-subscription-tier)
* [Subscription expiry](#subscription-expiry)
* [Self-managed GitLab data](#self-managed-gitlab-data)
* [CI pipeline minutes](#ci-pipeline-minutes)
* [Purchasing additional CI minutes](#purchasing-additional-ci-minutes)
* [Contact Support](#contact-support)
* [GitLab for Education subscriptions](#gitlab-for-education-subscriptions)
* [GitLab for Open Source subscriptions](#gitlab-for-open-source-subscriptions)
# GitLab subscription[](#gitlab-subscription "Permalink")
GitLab 提供了多層功能. 您的訂閱決定了您有權訪問的層. 訂閱有效期為 12 個月.
GitLab 為[GitLab 教育計劃](https://about.gitlab.com/solutions/education/)和[GitLab 開源計劃的](https://about.gitlab.com/solutions/open-source/)參與者提供特殊訂閱. 有關獲取和續訂這些訂閱的詳細信息,請參閱:
* [GitLab for Education subscriptions](#gitlab-for-education-subscriptions)
* [GitLab for Open Source subscriptions](#gitlab-for-open-source-subscriptions)
## Choosing a GitLab subscription[](#choosing-a-gitlab-subscription "Permalink")
選擇訂閱時,請考慮以下因素:
* [GitLab tier](#choosing-a-gitlab-tier)
* [GitLab.com or self-managed](#choosing-between-gitlabcom-or-self-managed)
* [Group or personal subscription (GitLab.com only)](#choosing-a-gitlabcom-group-or-personal-subscription)
* [Number of users](#choosing-the-number-of-users)
### Choosing a GitLab tier[](#choosing-a-gitlab-tier "Permalink")
定價[基于層級](https://about.gitlab.com/pricing/) ,使您可以選擇適合預算的功能. 請參閱[GitLab.com 功能比較](https://about.gitlab.com/pricing/gitlab-com/feature-comparison/)和[自我管理功能比較,](https://about.gitlab.com/pricing/self-managed/feature-comparison/)以獲取有關每種產品在每個層上可用的[功能](https://about.gitlab.com/pricing/self-managed/feature-comparison/)的信息.
### Choosing between GitLab.com or self-managed[](#choosing-between-gitlabcom-or-self-managed "Permalink")
訂閱的應用方式有所不同,具體取決于您使用的是 GitLab.com 還是自我管理的實例.
* [GitLab.com:GitLab](#gitlabcom)的軟件即服務產品. 您無需安裝任何程序即可使用 GitLab.com,只需[注冊](https://gitlab.com/users/sign_up)并立即開始使用 GitLab.
* [GitLab 自我管理](#self-managed) :安裝,管理和維護自己的 GitLab 實例.
在自我管理的實例上,GitLab 訂閱為所有用戶提供了相同的功能集. 在 GitLab.com 上,您可以將訂閱應用于組或個人名稱空間.
**注意:**訂閱不能在 GitLab.com 和 GitLab 自我管理之間轉移. 必須購買新訂閱并根據需要應用.
### Choosing a GitLab.com group or personal subscription[](#choosing-a-gitlabcom-group-or-personal-subscription "Permalink")
在 GitLab.com 上,您可以將訂閱應用于組或個人名稱空間.
適用于:
* GitLab.com 上的**組** ,組,所有子組以及所選組下的所有項目將具有關聯層的功能. GitLab 建議在管理組織的項目和用戶時選擇一個小組計劃.
* 作為**個人用戶空間** ,所有項目都將具有應用了訂閱的功能,但是由于它不是一個組,因此將無法使用組功能.
### Choosing the number of users[](#choosing-the-number-of-users "Permalink")
訂閱中的計數對象之間有一些不同,具體取決于您使用的是 GitLab.com 還是自我管理的實例.
#### GitLab.com[](#gitlabcom "Permalink")
GitLab.com 訂閱使用并發( *座位* )模型. 您需要根據一次啟用的最大用戶數來支付訂閱費用. 您可以在訂閱期間添加和刪除用戶,只要在任何給定時間的總用戶數都在訂閱數之內即可.
預訂中將計算每個已占用的席位,無論是按人員,職位還是漫游器,但以下情況除外:
* 具有金牌訂閱的訪客權限的成員.
**提示:**為了支持開源社區并鼓勵開發開源項目,GitLab 授予所有 GitLab.com **公共**項目訪問**金牌**功能的權限,無論其訂閱如何.
#### Self-managed[](#self-managed "Permalink")
自我管理的訂閱使用混合模型. 您需要根據訂閱期內啟用的最大用戶數來支付訂閱費用. 對于非脫機或封閉網絡上的實例,每季度使用[Seat Link](#seat-link)檢查一次自我管理安裝中的最大同時用戶數.
預訂中將計算每個已占用的席位,無論是按人員,工作還是漫游方式,但以下情況除外:
* 在訂閱續訂之前受到限制的[停用](../user/admin_area/activating_deactivating_users.html#deactivating-a-user)和[阻止的](../user/admin_area/blocking_unblocking_users.html)用戶不會被視為續訂訂閱的活動用戶. 在最初添加他們的訂閱期內,他們可以算作活動用戶.
* 具有 Ultimate 訂閱的 Guest 權限的成員.
* GitLab 創建的服務帳戶: `Ghost User`和`Support Bot` .
##### Users statistics[](#users-statistics "Permalink")
要查看實例中用戶的細分,包括活動,計費和已阻止,請轉至**管理區域>概述>儀表板,**然后在" **用戶"**部分中選擇" **用戶統計信息** ". 有關更多詳細信息,請參閱[用戶統計信息](../user/admin_area/index.html#users-statistics) .
**注意:**如果啟用了 LDAP 集成,則配置域中的任何人都可以注冊一個 GitLab 帳戶. 續訂時可能會導致意外的賬單. 考慮[禁用新注冊](../user/admin_area/settings/sign_up_restrictions.html)并改為手動管理新用戶.
## Obtain a GitLab subscription[](#obtain-a-gitlab-subscription "Permalink")
### Subscribe to GitLab.com[](#subscribe-to-gitlabcom "Permalink")
訂閱 GitLab.com:
1. 使用我們的[注冊頁面](https://gitlab.com/users/sign_in#register-pane)為您自己創建一個用戶帳戶.
2. 創建一個[組](../user/group/index.html) . GitLab 組幫助將相關項目組合在一起,使您可以一次授予成員訪問多個項目的權限. 如果您計劃在個人名稱空間中包含項目,則不需要組.
3. 創建其他用戶并將其[添加到組中](../user/group/index.html#add-users-to-a-group) .
4. 通過[客戶門戶](https://customers.gitlab.com/)選擇**青銅** , **銀**或**金** GitLab.com 計劃.
5. 將您的 GitLab.com 帳戶與客戶門戶帳戶關聯. 選擇計劃后,如果尚未鏈接您的帳戶,系統將提示您使用" **登錄到 GitLab.com"**按鈕來鏈接您的帳戶.
6. 從下拉列表中選擇名稱空間以關聯預訂.
7. 進行結算.
**提示:**您也可以轉到" [**我的帳戶"**](https://customers.gitlab.com/customers/edit)頁面來添加或更改 GitLab.com 帳戶鏈接.
### Subscribe through GitLab self-managed[](#subscribe-through-gitlab-self-managed "Permalink")
要通過自我管理安裝訂閱 GitLab:
1. 轉到[客戶門戶](https://customers.gitlab.com/)并購買**Starter** , **Premium**或**Ultimate**自我管理計劃.
2. 購買后,許可證文件將發送到與客戶門戶帳戶關聯的電子郵件地址,該電子郵件地址必須[上傳到您的 GitLab 實例](../user/admin_area/license.html#uploading-your-license) .
**提示:**如果您要購買現有**Core**自管實例的訂閱,請確保購買的席位足以[覆蓋您的用戶](../user/admin_area/index.html#administering-users) .
## Manage your GitLab account[](#manage-your-gitlab-account "Permalink")
使用[客戶門戶,](https://customers.gitlab.com/)您可以:
* [Change billing and company information](#change-billing-information)
* [Change the payment method](#change-payment-method)
* [Change the linked account](#change-the-linked-account)
* [Change the associated namespace](#change-the-associated-namespace)
* [Change customers portal account password](#change-customer-portal-account-password)
### Change billing information[](#change-billing-information "Permalink")
要更改帳單信息:
1. 登錄到[客戶門戶](https://customers.gitlab.com/customers/sign_in) .
2. 選擇**我的帳戶**下拉菜單,然后點擊**付款方式** .
3. 對" **帳戶詳細**信息"進行必要的更改.
4. Click **保存更改**.
**注意:**將來的購買將使用此部分中的信息. 本節中列出的電子郵件用于客戶門戶登錄以及與許可證相關的電子郵件通信.
### Change payment method[](#change-payment-method "Permalink")
要更改付款方式或更新信用卡信息:
1. 登錄到[客戶門戶](https://customers.gitlab.com/customers/sign_in) .
2. 選擇**我的帳戶**下拉菜單,然后點擊**付款方式** .
3. **編輯**現有的付款方式信息或**添加新的付款方式** .
4. 保存更改.
### Change the linked account[](#change-the-linked-account "Permalink")
要更改與您的客戶門戶帳戶關聯的 GitLab.com 帳戶:
1. 登錄到[客戶門戶](https://customers.gitlab.com/customers/sign_in) .
2. 在單獨的瀏覽器選項卡中,轉到[GitLab.com,](https://gitlab.com)并確保您尚未登錄.
3. 在"客戶門戶"頁面上,單擊**我的帳戶>帳戶詳細信息** .
4. 在**您的 GitLab.com 帳戶下** ,單擊" **更改關聯的帳戶"** .
5. 登錄到要鏈接到"客戶門戶"帳戶的[GitLab.com](https://gitlab.com)帳戶.
### Change the associated namespace[](#change-the-associated-namespace "Permalink")
使用關聯的 GitLab.com 帳戶:
1. 登錄到[客戶門戶](https://customers.gitlab.com/customers/sign_in) .
2. 導航到" **管理購買"**頁面.
3. Click **更改鏈接的名稱空間**.
4. 從" **此訂閱用于"**下拉列表中選擇所需的組.
5. Click **進行結算**.
訂閱費用是根據一個組中的用戶總數(包括其子組和嵌套項目)來計算的. 如果用戶總數超過了訂閱中的席位數,則將向您收取額外的用戶費用.
### Change customer portal account password[](#change-customer-portal-account-password "Permalink")
要更改此客戶門戶帳戶的密碼:
1. 登錄到[客戶門戶](https://customers.gitlab.com/customers/sign_in) .
2. 選擇**我的帳戶**下拉菜單,然后點擊**帳戶詳細信息** .
3. 對**您的密碼**部分進行必要的更改.
4. Click **保存更改**.
## View your subscription[](#view-your-subscription "Permalink")
### View your GitLab.com subscription[](#view-your-gitlabcom-subscription "Permalink")
要查看您的 GitLab.com 訂閱狀態,請登錄 GitLab.com 并轉到相關名稱空間的**Billing**部分:
* 對于個人:
1. 轉到**用戶頭像>設置** .
2. 點擊**結算** .
* 對于團體:
1. 在群組頁面( *而不是*群組中的項目)中,轉到**設置>結算** .
下表描述了您的組訂閱詳細信息:
| Field | Description |
| --- | --- |
| 訂閱席 | 如果這是付費計劃,則表示您已支付支持該組座位的數量. |
| 當前使用的座椅 | 當前正在使用的活動座位數. |
| 最多使用的座位 | 您使用過的最高座位數. 如果這超出了訂閱的席位,則您可能欠其他用戶額外的費用. |
| 欠座位 | 如果您使用的最大席位超出了訂閱中的席位,您將為已添加的用戶欠額外的費用. |
| 訂閱開始日期 | 訂閱開始的日期. 如果這是免費計劃,則是您從組的付費計劃過渡的日期. |
| 訂閱結束日期 | 當前訂閱的終止日期. 不適用于免費計劃. |
### View your self-managed subscription[](#view-your-self-managed-subscription "Permalink")
要查看您的自我管理訂閱的狀態,請登錄到自我管理實例,然后轉到" **許可證"**頁面.
1. 去 **管理區** .
2. 從左側菜單中選擇**許可證** .
## Renew your subscription[](#renew-your-subscription "Permalink")
要續訂您的訂閱,請[通過查看您的帳戶來準備續訂](#prepare-for-renewal-by-reviewing-your-account) ,然后執行以下一項操作:
* [Renew a GitLab.com subscription](#renew-or-change-a-gitlabcom-subscription).
* [Renew a self-managed subscription](#renew-a-self-managed-subscription).
### Prepare for renewal by reviewing your account[](#prepare-for-renewal-by-reviewing-your-account "Permalink")
[客戶門戶](https://customers.gitlab.com/customers/sign_in)是您續訂和修改訂閱的工具. 在進行續訂之前,請登錄并驗證或更新:
* **帳戶詳細信息**頁面上的發票聯系方式.
* 在" **付款方式"**頁面上存檔的信用卡.
**提示:**如果您需要訪問客戶門戶的幫助或需要更改管理您的訂閱的聯系人,請與我們的[支持團隊](https://support.gitlab.com/hc/en-us/requests/new?ticket_form_id=360000071293)聯系.
定期檢查您的用戶帳戶很重要,因為:
* GitLab 訂閱基于用戶數量. 如果為太多的用戶續訂,則您將支付比應支付的更多的費用,而如果您嘗試為太少的用戶續訂訂閱,則續訂將失敗.
* 過時的用戶帳戶可能會帶來安全風險. 定期檢查有助于降低這種風險.
#### Users over License[](#users-over-license "Permalink")
GitLab 訂閱對特定數量的用戶有效. 有關詳細信息,請參閱[選擇用戶數](#choosing-the-number-of-users) . 如果活動用戶數超過了訂閱中包含的數量,即*超過許可證*的*用戶*數,則必須在續訂之前或續訂時為超出的用戶數付費. 這也稱為*真正的升級*過程.
##### Purchase additional seats for GitLab.com[](#purchase-additional-seats-for-gitlabcom "Permalink")
沒有自助服務選項可以購買額外的座位. 您必須從 GitLab 銷售處索取報價. 為此,請通過我們的[支持表格](https://support.gitlab.com/hc/en-us/requests/new?ticket_form_id=360000071293)聯系 GitLab.
每個座位收取的費用是通過以下方法之一計算的:
* 如果在續訂前付費,則每個座位的數量將按比例計算. 例如,如果在訂閱期結束前 3 個月添加了用戶,則應付款額的計算方式為:(3/12)x 年費.
* 如果在續簽時支付,則每個席位的金額為標準年費.
##### Purchase additional users for self-managed[](#purchase-additional-users-for-self-managed "Permalink")
自我管理實例可以在訂閱期間的任何時間將用戶添加到訂閱中. 訂閱期內添加的其他用戶的成本是從購買之日起到訂閱期結束之間按比例分配的.
要將用戶添加到訂閱中:
1. 登錄到[客戶門戶](https://customers.gitlab.com/) .
2. 導航到" **管理購買"**頁面.
3. 選擇相關訂閱卡上的**添加更多席位** .
4. 輸入其他用戶數.
5. Select **進行結算**.
6. 查看**訂閱升級詳細信息** . 系統會列出系統上所有用戶的總價,以及您已支付的款項的信用額. 您只需要支付零錢.
7. Select **確認升級**.
以下內容將通過電子郵件發送給您:
* 付款收據. 您也可以在客戶門戶的" [**查看發票"**](https://customers.gitlab.com/receipts)下訪問此信息.
* A new license. [Upload this license](../user/admin_area/license.html#uploading-your-license) to your instance to use it.
### Seat Link[](#seat-link "Permalink")
[Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/208832) in [GitLab Starter](https://about.gitlab.com/pricing/) 12.9.
利用 Seat Link,我們可以使用季度對帳流程為自助客戶提供按比例分配的費用,用于全年增加用戶.
Seat Link 每天將連接的自我管理實例中的所有用戶計數發送到 GitLab. 該信息用于自動按比例分配對帳. 數據通過加密的 HTTPS 連接安全地發送.
Seat Link **僅**向 GitLab 提供以下信息:
* Date
* License key
* 歷史最大用戶數
* 活動用戶數
對于離線或封閉網絡客戶,將使用現有[的調整模型](#users-over-license) . 如果沒有用戶計數數據,則無法按比例收取費用.
<details><summary title="Click here to view example content of a Seat Link POST request.">單擊此處查看 Seat Link POST 請求的示例內容.</summary>
```
{
date: '2020-01-29',
license_key: 'ZXlKa1lYUmhJam9pWm5WNmVsTjVZekZ2YTJoV2NucDBh
RXRxTTA5amQxcG1VMVZqDQpXR3RwZEc5SGIyMVhibmxuZDJ0NWFrNXJTVzVH
UzFCT1hHNVRiVFIyT0ZaUFlVSm1OV1ZGV0VObE1uVk4NCk4xY3ZkM1F4Y2to
MFFuVklXSFJvUWpSM01VdE9SVE5rYkVjclZrdDJORkpOTlhka01qaE5aalpj
YmxSMg0KWVd3MFNFTldTRmRtV1ZGSGRDOUhPR05oUVZvNUsxVnRXRUZIZFU1
U1VqUm5aVFZGZUdwTWIxbDFZV1EyDQphV1JTY1V4c1ZYSjNPVGhrYVZ4dVlu
TkpWMHRJZUU5dmF6ZEJRVVkxTlVWdFUwMTNSMGRHWm5SNlJFcFYNClQyVkJl
VXc0UzA0NWFFb3ZlSFJrZW0xbVRqUlZabkZ4U1hWcWNXRnZYRzVaTm5GSmVW
UnJVR1JQYTJKdA0KU0ZZclRHTmFPRTVhZEVKMUt6UjRkSE15WkRCT1UyNWlS
MGRJZDFCdmRFWk5Za2h4Tm5sT1VsSktlVlYyDQpXRmhjYmxSeU4wRnRNMU5q
THpCVWFGTmpTMnh3UWpOWVkyc3pkbXBST1dnelZHY3hUV3hxVDIwdlZYRlQN
Ck9EWTJSVWx4WlVOT01EQXhVRlZ3ZGs1Rk0xeHVSVEJTTDFkMWJUQTVhV1ZK
WjBORFdWUktaRXNyVnpsTw0KTldkWWQwWTNZa05VWlZBMmRUVk9kVUpxT1hV
Mk5VdDFTUzk0TUU5V05XbFJhWGh0WEc1cVkyWnhaeTlXDQpTMEpyZWt0cmVY
bzBOVGhFVG1oU1oxSm5WRFprY0Uwck0wZEdhVUpEV1d4a1RXZFRjVU5tYTB0
a2RteEQNCmNWTlFSbFpuWlZWY2JpdFVVbXhIV0d4MFRuUnRWbkJKTkhwSFJt
TnRaMGsyV0U1MFFUUXJWMUJVTWtOSA0KTVhKUWVGTkxPVTkzV1VsMlVUUldk
R3hNTWswNU1USlNjRnh1U1UxTGJTdHRRM1l5YTFWaWJtSlBTMkUxDQplRkpL
SzJSckszaG1hVXB1ZVRWT1UwdHZXV0ZOVG1WamMyVjRPV0pSUlZkUU9UUnpU
VWh2Wlc5cFhHNUgNClNtRkdVMDUyY1RGMWNGTnhVbU5JUkZkeGVWcHVRMnBh
VTBSUGR6VnRNVGhvWTFBM00zVkZlVzFOU0djMA0KY1ZFM1FWSlplSFZ5UzFS
aGIxTmNia3BSUFQxY2JpSXNJbxRsZVNJNkltZFhiVzFGVkRZNWNFWndiV2Rt
DQpNWEIyY21SbFFrdFNZamxaYURCdVVHcHhiRlV3Tm1WQ2JGSlFaSFJ3Y0Rs
cFMybGhSMnRPTkZOMWNVNU0NClVGeHVTa3N6TUUxcldVOTVWREl6WVVWdk5U
ZGhWM1ZvVjJkSFRtZFBZVXRJTkVGcE55dE1NRE5dWnpWeQ0KWlV0aWJsVk9T
RmRzVVROUGRHVXdWR3hEWEc1MWjWaEtRMGQ2YTAxWFpUZHJURTVET0doV00w
ODRWM0V2DQphV2M1YWs5cWFFWk9aR3BYTm1aVmJXNUNaazlXVUVRMWRrMXpj
bTFDV0V4dldtRmNibFpTTWpWU05VeFMNClEwTjRNMWxWCUtSVGEzTTJaV2xE
V0hKTFRGQmpURXRsZFVaQlNtRnJTbkpPZGtKdlUyUmlNVWxNWWpKaQ0KT0dw
c05YbE1kVnh1YzFWbk5VZDFhbU56ZUM5Tk16TXZUakZOVW05cVpsVTNObEo0
TjJ4eVlVUkdkWEJtDQpkSHByYWpreVJrcG9UVlo0Y0hKSU9URndiV2RzVFdO
VlhHNXRhVmszTkV0SVEzcEpNMWRyZEVoRU4ydHINCmRIRnFRVTlCVUVVM1pV
SlRORE4xUjFaYVJGb3JlWGM5UFZ4dUlpd2lhWFlpt2lKV00yRnNVbk5RTjJk
Sg0KU1hNMGExaE9SVGR2V2pKQlBUMWNiaUo5DQo=',
max_historical_user_count: 10,
active_users: 6
}
```</details>
您可以在管理面板中查看確切的 JSON 有效負載. 要查看有效負載:
1. 導航到" **管理區域">"設置">"度量和分析",**然后展開" **Seat Link"** .
2. Click **預覽有效載荷**.
#### Disable Seat Link[](#disable-seat-link "Permalink")
[Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/212375) in [GitLab Starter](https://about.gitlab.com/pricing/) 12.10.
默認情況下,Seat Link 已啟用.
要禁用此功能,請轉到 **在管理區域>設置>指標和配置文件中** ,取消選中" **啟用座椅鏈接"**復選框>" **保存更改"** .
要在 Omnibus GitLab 安裝中禁用 Seat Link,并防止日后通過管理面板對其進行配置,請在[`gitlab.rb`](https://docs.gitlab.com/omnibus/settings/configuration.html)設置以下[`gitlab.rb`](https://docs.gitlab.com/omnibus/settings/configuration.html) :
```
gitlab_rails['seat_link_enabled'] = false
```
要在 GitLab 源代碼安裝中禁用 Seat Link,并防止日后通過管理面板對其進行配置,請在`gitlab.yml`進行以下設置:
```
production: &base
# ...
gitlab:
# ...
seat_link_enabled: false
```
### Renew or change a GitLab.com subscription[](#renew-or-change-a-gitlabcom-subscription "Permalink")
要更新為更多的用戶比你們 GitLab.com 系統目前正在積極,請聯系我們通過銷售團隊`renewals@gitlab.com`尋求幫助,因為這不能在客戶門戶網站來完成.
For details on upgrading your subscription tier, see [Upgrade your GitLab.com subscription tier](#upgrade-your-gitlabcom-subscription-tier).
#### Automatic renewal[](#automatic-renewal "Permalink")
要查看或更改自動訂閱續訂(與上一周期位于同一層),請登錄到[客戶門戶](https://customers.gitlab.com/customers/sign_in) ,然后:
* 如果您看到" **恢復訂閱"**按鈕,則您的訂閱先前已被取消. 單擊它可以恢復自動續訂.
* 如果看到" **取消訂閱"** ,則您的訂閱將設置為在訂閱期結束時自動續訂. 單擊它可以取消自動續訂.
啟用自動續訂后,訂閱將在到期日期自動續訂,并且可用服務之間不會有任何差距. 將會生成一張用于續訂的發票,并且可以在" [查看發票"](https://customers.gitlab.com/receipts)頁面中查看或下載. 如果您在續訂過程中遇到困難,請聯系我們的[支持團隊](https://support.gitlab.com/hc/en-us/requests/new?ticket_form_id=360000071293)以尋求幫助.
### Renew a self-managed subscription[](#renew-a-self-managed-subscription "Permalink")
從訂閱到期前 30 天開始,GitLab 會在 GitLab 用戶界面中用標語通知管理員到期日期.
我們建議您在續訂期間執行以下步驟:
1. 通過[阻止](../user/admin_area/blocking_unblocking_users.html#blocking-a-user)任何不活躍或不需要的用戶來修剪[它們](../user/admin_area/blocking_unblocking_users.html#blocking-a-user) .
2. 確定在即將到來的訂閱中是否需要增加用戶.
3. 登錄到[客戶門戶,](https://customers.gitlab.com/customers/sign_in)然后選擇現有訂閱下的" **續訂"**按鈕.
**提示:**如果您需要更改您的[GitLab 層](https://about.gitlab.com/pricing/) ,請通過`renewals@gitlab.com`與我們的銷售團隊聯系以尋求幫助,因為這不能在客戶門戶中完成.
4. 在第一個框中,輸入來年需要的用戶許可總數. 確保此數目至少**等于或大于**執行更新時系統中的活動用戶數.
5. 在第二個框中,輸入上一個訂購期限內發生的用戶超額[使用的許可證超用戶](#users-over-license)數.
**提示:**您可以*通過以下方式*在實例的**管理**控制臺中找到獲得*許可*的*用戶* **:** (頂部)中的( **管理區域** ),或轉到`/admin` .
下表介紹了管理控制臺和續訂條款的詳細信息:
| Field | Description |
| --- | --- |
| 許可中的用戶 | 您在系統上加載的當前許可證中已付費的用戶數. 這不包括您在續訂期間`Users over license`向`Users over license`支付的金額. |
| 活躍用戶 | 系統上當前的活動用戶數. |
| 最大用戶 | 在已加載許可證有效期內,系統上活動用戶數最多. 如果此數字在任何時候都超出了許可數量的用戶,則會使用戶蒙受許可數量的困擾. |
| 超過許可的用戶 | 在當前許可期限內,超出`Users in License`用戶數量的用戶數量. 此數量的用戶將在下次續訂時付費. |
6. 查看您的續訂詳細信息并完成付款過程.
7. 可以在相關訂閱卡上的" [管理購買"](https://customers.gitlab.com/subscriptions)頁面上下載續訂期限的許可證. 選擇**將許可證復制到剪貼板**或選擇**下載許可證**以獲取副本.
8. 將新許可證[上載到](../user/admin_area/license.html#uploading-your-license)您的實例.
將會生成一張用于續訂的發票,并且可以在" [查看發票"](https://customers.gitlab.com/receipts)頁面上查看或下載. 如果您在續訂過程中遇到困難,請聯系我們的[支持團隊](https://support.gitlab.com/hc/en-us/requests/new?ticket_form_id=360000071293)以尋求幫助.
## Upgrade your subscription tier[](#upgrade-your-subscription-tier "Permalink")
升級過程因您是 GitLab.com 還是自我管理的客戶而異.
### Upgrade your GitLab.com subscription tier[](#upgrade-your-gitlabcom-subscription-tier "Permalink")
要升級您的[GitLab 層](https://about.gitlab.com/pricing/) :
1. 登錄到[客戶門戶](https://customers.gitlab.com/customers/sign_in) .
2. 在" [管理購買"](https://customers.gitlab.com/subscriptions)頁面上,選擇相關訂閱卡上的" **升級"**按鈕.
3. 選擇所需的升級.
4. 確認有效的付款方式,或添加新的付款方式.
5. 選中**我接受隱私政策和服務條款**復選框.
6. Select **確認購買**.
處理完購買后,您將收到新訂閱等級的確認.
### Upgrade your self-managed subscription tier[](#upgrade-your-self-managed-subscription-tier "Permalink")
要升級您的[GitLab 層](https://about.gitlab.com/pricing/) ,請聯系我們的銷售團隊,因為這不能在客戶門戶中完成. 您可以發送電子郵件至`renewals@gitlab.com`或填寫" [**聯系銷售"**](https://about.gitlab.com/sales/)表單. 在消息中包括要升級的訂閱的詳細信息以及所需的層.
After messaging the sales team, the workflow is as follows:
1. 收到銷售團隊的答復,要求確認升級.
2. 回復銷售團隊,確認升級細節.
3. 收到銷售團隊的報價.
4. 簽名并返回報價.
5. 收到新許可證.
6. 上載新許可證. 有關詳細信息,請參閱上[載許可證](../user/admin_area/license.html#uploading-your-license) .
上載許可證文件后,新的訂閱層將處于活動狀態.
## Subscription expiry[](#subscription-expiry "Permalink")
當您的訂閱或試用版到期時,GitLab 不會刪除您的數據,但是根據到期時的層級,它可能變得不可訪問. 如果您沒有準備好到期,則某些功能可能無法達到預期的效果. 例如, [未傳遞特定](https://gitlab.com/gitlab-org/gitlab/-/issues/24759)于[環境的變量](https://gitlab.com/gitlab-org/gitlab/-/issues/24759) .
如果您續訂或升級,您的數據將再次可訪問.
### Self-managed GitLab data[](#self-managed-gitlab-data "Permalink")
對于自我管理的客戶,有 14 天的寬限期,您的功能將繼續按原樣運行,此后整個實例將變為只讀狀態.
但是,如果刪除許可證,您將立即恢復為核心功能,并且實例將再次被讀取/寫入.
## CI pipeline minutes[](#ci-pipeline-minutes "Permalink")
CI 管道分鐘數是您在 GitLab 共享運行程序上的[管道](../ci/pipelines/index.html)的執行時間. 每個[GitLab.com 層均](https://about.gitlab.com/pricing/)包含 CI 管道分鐘的每月配額:
* 免費:2,000 分鐘
* 青銅:2,000 分鐘
* Silver: 10,000 minutes
* 金牌:50,000 分鐘
配額適用于:
* 組,其中在組的所有成員,其子組和嵌套項目之間共享分鐘. 要查看該組的使用情況,請導航至該組,然后 **設置** > **使用配額** .
* 您的個人帳戶,其中可用于您的個人項目的紀要. 要查看和購買個人會議記錄,請點擊您的頭像,然后 **設置** > **[使用配額](https://gitlab.com/profile/usage_quotas#pipelines-quota-tab)** .
只有 GitLab 共享運行程序的管道時間受到限制. 如果您為項目設置了特定的運行器,則在 GitLab.com 上的構建時間沒有限制.
可用配額在每個日歷月的第一個 UTC 午夜重置.
CI 分鐘數用完后,會自動發送一封電子郵件以通知名稱空間的所有者. 您可以[購買其他 CI 分鐘](#purchasing-additional-ci-minutes) ,或者將帳戶升級為[Silver 或 Gold](https://about.gitlab.com/pricing/) . 即使您達到極限,仍然可以使用您自己的跑步者.
### Purchasing additional CI minutes[](#purchasing-additional-ci-minutes "Permalink")
如果您使用的是 GitLab.com,則可以購買額外的 CI 分鐘,這樣在使用完您的主要配額中的所有 CI 分鐘后,管道不會被阻塞. 您可以在[GitLab 客戶門戶中](https://customers.gitlab.com/plans)找到其他 CI / CD 分鐘的價格. 其他分鐘:
* 僅在訂閱中包含的共享配額用完后才使用.
* 逐月滾動.
要在 GitLab.com 上為您的小組購買更多時間:
1. 在您的小組中,轉到 **設置>使用配額** .
2. 選擇**購買其他分鐘** ,您將被帶到客戶門戶.
3. 在 GitLab.com 上找到與您的小組鏈接的訂閱卡,單擊" **購買更多 CI 分鐘"** ,然后完成有關交易的詳細信息.
4. 處理完您的付款后,多余的 CI 分鐘將同步到您的組名稱空間.
5. 要確認可用的 CI 分鐘,請轉到您的小組,然后 **設置>使用配額** .
The **額外的分鐘** displayed now includes the purchased additional CI minutes, plus any minutes rolled over from last month.
要為您的個人命名空間購買更多分鐘,請執行以下操作:
1. 單擊您的頭像,然后轉到**設置>使用配額** .
2. 選擇**購買其他分鐘** ,您將被帶到客戶門戶.
3. 在 GitLab.com 上找到鏈接到您的個人命名空間的訂閱卡,單擊" **購買更多 CI 分鐘"** ,然后完成有關交易的詳細信息. 我們處理完您的付款后,多余的 CI 分鐘將同步到您的個人名稱空間.
4. 要確認您的個人項目可用的 CI 分鐘,請單擊您的頭像,然后轉到**設置>使用配額** .
現在顯示的" **其他分鐘"**包括已購買的其他配置項分鐘,以及上個月結轉的所有分鐘.
意識到:
* 如果您在購買付費計劃之前購買了額外的 CI 分鐘數,我們將為您的付費計劃按比例計算費用. 這意味著您可能需要不到一年的費用,因為您之前是使用額外的 CI 分鐘創建訂閱的.
* 一旦將額外的 CI 分鐘分配給一個組,就無法將其轉移到另一個組.
* 如果您使用的分鐘數超出了默認配額,則這些分鐘數將在您購買額外的分鐘數后立即從"其他分鐘數"配額中扣除.
## Contact Support[](#contact-support "Permalink")
我們還鼓勵所有用戶在項目跟蹤器中搜索[GitLab](https://gitlab.com/gitlab-org/gitlab/-/issues/)項目中的已知問題和現有功能要求.
這些問題是獲取特定產品計劃的更新以及直接與相關 GitLab 團隊成員進行溝通的最佳途徑.
學習更多關于:
* [GitLab 支持](https://about.gitlab.com/support/)的層次.
* [Submit a request via the Support Portal](https://support.gitlab.com/hc/en-us/requests/new).
## GitLab for Education subscriptions[](#gitlab-for-education-subscriptions "Permalink")
要續訂[GitLab for Education](https://about.gitlab.com/solutions/education/)訂閱,請發送電子郵件至`education@gitlab.com`其中包含以下信息:
1. 續訂的座位數. 您可以根據需要添加座位.
2. 許可證的用例. 具體來說,我們需要驗證其使用是否符合《 [最終用戶許可協議》](https://about.gitlab.com/terms/#edu-oss)的條件. 請注意,大學的基礎設施運營和信息技術運營不在教育計劃的規定范圍之內. 有關詳細信息,請參見" [教育常見問題解答"](https://about.gitlab.com/solutions/education/#FAQ) .
3. 要簽署續訂報價的主要聯系人的全名,電子郵件地址和電話號碼. 只有代表大學的具有適當簽署權的教職員工簽署才能被接受.
收到上述信息后,我們將處理請求并返回續簽以供簽名. 請至少等待 2 個工作日才能退貨. 如有任何問題,請發送電子郵件至`education@gitlab.com` .
## GitLab for Open Source subscriptions[](#gitlab-for-open-source-subscriptions "Permalink")
所有的[GitLab for Open Source](https://about.gitlab.com/solutions/open-source/program/)請求(包括訂閱續訂)都必須通過應用程序進行. 如有任何疑問,請發送電子郵件至`opensource@gitlab.com`尋求幫助.
- GitLab Docs
- Installation
- Requirements
- GitLab cloud native Helm Chart
- Install GitLab with Docker
- Installation from source
- Install GitLab on Microsoft Azure
- Installing GitLab on Google Cloud Platform
- Installing GitLab on Amazon Web Services (AWS)
- Analytics
- Code Review Analytics
- Productivity Analytics
- Value Stream Analytics
- Kubernetes clusters
- Adding and removing Kubernetes clusters
- Adding EKS clusters
- Adding GKE clusters
- Group-level Kubernetes clusters
- Instance-level Kubernetes clusters
- Canary Deployments
- Cluster Environments
- Deploy Boards
- GitLab Managed Apps
- Crossplane configuration
- Cluster management project (alpha)
- Kubernetes Logs
- Runbooks
- Serverless
- Deploying AWS Lambda function using GitLab CI/CD
- Securing your deployed applications
- Groups
- Contribution Analytics
- Custom group-level project templates
- Epics
- Manage epics
- Group Import/Export
- Insights
- Issues Analytics
- Iterations
- Public access
- SAML SSO for GitLab.com groups
- SCIM provisioning using SAML SSO for GitLab.com groups
- Subgroups
- Roadmap
- Projects
- GitLab Secure
- Security Configuration
- Container Scanning
- Dependency Scanning
- Dependency List
- Static Application Security Testing (SAST)
- Secret Detection
- Dynamic Application Security Testing (DAST)
- GitLab Security Dashboard
- Offline environments
- Standalone Vulnerability pages
- Security scanner integration
- Badges
- Bulk editing issues and merge requests at the project level
- Code Owners
- Compliance
- License Compliance
- Compliance Dashboard
- Create a project
- Description templates
- Deploy Keys
- Deploy Tokens
- File finder
- Project integrations
- Integrations
- Atlassian Bamboo CI Service
- Bugzilla Service
- Custom Issue Tracker service
- Discord Notifications service
- Enabling emails on push
- GitHub project integration
- Hangouts Chat service
- Atlassian HipChat
- Irker IRC Gateway
- GitLab Jira integration
- Mattermost Notifications Service
- Mattermost slash commands
- Microsoft Teams service
- Mock CI Service
- Prometheus integration
- Redmine Service
- Slack Notifications Service
- Slack slash commands
- GitLab Slack application
- Webhooks
- YouTrack Service
- Insights
- Issues
- Crosslinking Issues
- Design Management
- Confidential issues
- Due dates
- Issue Boards
- Issue Data and Actions
- Labels
- Managing issues
- Milestones
- Multiple Assignees for Issues
- Related issues
- Service Desk
- Sorting and ordering issue lists
- Issue weight
- Associate a Zoom meeting with an issue
- Merge requests
- Allow collaboration on merge requests across forks
- Merge Request Approvals
- Browser Performance Testing
- How to create a merge request
- Cherry-pick changes
- Code Quality
- Load Performance Testing
- Merge Request dependencies
- Fast-forward merge requests
- Merge when pipeline succeeds
- Merge request conflict resolution
- Reverting changes
- Reviewing and managing merge requests
- Squash and merge
- Merge requests versions
- Draft merge requests
- Members of a project
- Migrating projects to a GitLab instance
- Import your project from Bitbucket Cloud to GitLab
- Import your project from Bitbucket Server to GitLab
- Migrating from ClearCase
- Migrating from CVS
- Import your project from FogBugz to GitLab
- Gemnasium
- Import your project from GitHub to GitLab
- Project importing from GitLab.com to your private GitLab instance
- Import your project from Gitea to GitLab
- Import your Jira project issues to GitLab
- Migrating from Perforce Helix
- Import Phabricator tasks into a GitLab project
- Import multiple repositories by uploading a manifest file
- Import project from repo by URL
- Migrating from SVN to GitLab
- Migrating from TFVC to Git
- Push Options
- Releases
- Repository
- Branches
- Git Attributes
- File Locking
- Git file blame
- Git file history
- Repository mirroring
- Protected branches
- Protected tags
- Push Rules
- Reduce repository size
- Signing commits with GPG
- Syntax Highlighting
- GitLab Web Editor
- Web IDE
- Requirements Management
- Project settings
- Project import/export
- Project access tokens (Alpha)
- Share Projects with other Groups
- Snippets
- Static Site Editor
- Wiki
- Project operations
- Monitor metrics for your CI/CD environment
- Set up alerts for Prometheus metrics
- Embedding metric charts within GitLab-flavored Markdown
- Embedding Grafana charts
- Using the Metrics Dashboard
- Dashboard YAML properties
- Metrics dashboard settings
- Panel types for dashboards
- Using Variables
- Templating variables for metrics dashboards
- Prometheus Metrics library
- Monitoring AWS Resources
- Monitoring HAProxy
- Monitoring Kubernetes
- Monitoring NGINX
- Monitoring NGINX Ingress Controller
- Monitoring NGINX Ingress Controller with VTS metrics
- Alert Management
- Error Tracking
- Tracing
- Incident Management
- GitLab Status Page
- Feature Flags
- GitLab CI/CD
- GitLab CI/CD pipeline configuration reference
- GitLab CI/CD include examples
- Introduction to CI/CD with GitLab
- Getting started with GitLab CI/CD
- How to enable or disable GitLab CI/CD
- Using SSH keys with GitLab CI/CD
- Migrating from CircleCI
- Migrating from Jenkins
- Auto DevOps
- Getting started with Auto DevOps
- Requirements for Auto DevOps
- Customizing Auto DevOps
- Stages of Auto DevOps
- Upgrading PostgreSQL for Auto DevOps
- Cache dependencies in GitLab CI/CD
- GitLab ChatOps
- Cloud deployment
- Docker integration
- Building Docker images with GitLab CI/CD
- Using Docker images
- Building images with kaniko and GitLab CI/CD
- GitLab CI/CD environment variables
- Predefined environment variables reference
- Where variables can be used
- Deprecated GitLab CI/CD variables
- Environments and deployments
- Protected Environments
- GitLab CI/CD Examples
- Test a Clojure application with GitLab CI/CD
- Using Dpl as deployment tool
- Testing a Phoenix application with GitLab CI/CD
- End-to-end testing with GitLab CI/CD and WebdriverIO
- DevOps and Game Dev with GitLab CI/CD
- Deploy a Spring Boot application to Cloud Foundry with GitLab CI/CD
- How to deploy Maven projects to Artifactory with GitLab CI/CD
- Testing PHP projects
- Running Composer and NPM scripts with deployment via SCP in GitLab CI/CD
- Test and deploy Laravel applications with GitLab CI/CD and Envoy
- Test and deploy a Python application with GitLab CI/CD
- Test and deploy a Ruby application with GitLab CI/CD
- Test and deploy a Scala application to Heroku
- GitLab CI/CD for external repositories
- Using GitLab CI/CD with a Bitbucket Cloud repository
- Using GitLab CI/CD with a GitHub repository
- GitLab Pages
- GitLab Pages
- GitLab Pages domain names, URLs, and baseurls
- Create a GitLab Pages website from scratch
- Custom domains and SSL/TLS Certificates
- GitLab Pages integration with Let's Encrypt
- GitLab Pages Access Control
- Exploring GitLab Pages
- Incremental Rollouts with GitLab CI/CD
- Interactive Web Terminals
- Optimizing GitLab for large repositories
- Metrics Reports
- CI/CD pipelines
- Pipeline Architecture
- Directed Acyclic Graph
- Multi-project pipelines
- Parent-child pipelines
- Pipelines for Merge Requests
- Pipelines for Merged Results
- Merge Trains
- Job artifacts
- Pipeline schedules
- Pipeline settings
- Triggering pipelines through the API
- Review Apps
- Configuring GitLab Runners
- GitLab CI services examples
- Using MySQL
- Using PostgreSQL
- Using Redis
- Troubleshooting CI/CD
- GitLab Package Registry
- GitLab Container Registry
- Dependency Proxy
- GitLab Composer Repository
- GitLab Conan Repository
- GitLab Maven Repository
- GitLab NPM Registry
- GitLab NuGet Repository
- GitLab PyPi Repository
- API Docs
- API resources
- .gitignore API
- GitLab CI YMLs API
- Group and project access requests API
- Appearance API
- Applications API
- Audit Events API
- Avatar API
- Award Emoji API
- Project badges API
- Group badges API
- Branches API
- Broadcast Messages API
- Project clusters API
- Group clusters API
- Instance clusters API
- Commits API
- Container Registry API
- Custom Attributes API
- Dashboard annotations API
- Dependencies API
- Deploy Keys API
- Deployments API
- Discussions API
- Dockerfiles API
- Environments API
- Epics API
- Events
- Feature Flags API
- Feature flag user lists API
- Freeze Periods API
- Geo Nodes API
- Group Activity Analytics API
- Groups API
- Import API
- Issue Boards API
- Group Issue Boards API
- Issues API
- Epic Issues API
- Issues Statistics API
- Jobs API
- Keys API
- Labels API
- Group Labels API
- License
- Licenses API
- Issue links API
- Epic Links API
- Managed Licenses API
- Markdown API
- Group and project members API
- Merge request approvals API
- Merge requests API
- Project milestones API
- Group milestones API
- Namespaces API
- Notes API
- Notification settings API
- Packages API
- Pages domains API
- Pipeline schedules API
- Pipeline triggers API
- Pipelines API
- Project Aliases API
- Project import/export API
- Project repository storage moves API
- Project statistics API
- Project templates API
- Projects API
- Protected branches API
- Protected tags API
- Releases API
- Release links API
- Repositories API
- Repository files API
- Repository submodules API
- Resource label events API
- Resource milestone events API
- Resource weight events API
- Runners API
- SCIM API
- Search API
- Services API
- Application settings API
- Sidekiq Metrics API
- Snippets API
- Project snippets
- Application statistics API
- Suggest Changes API
- System hooks API
- Tags API
- Todos API
- Users API
- Project-level Variables API
- Group-level Variables API
- Version API
- Vulnerabilities API
- Vulnerability Findings API
- Wikis API
- GraphQL API
- Getting started with GitLab GraphQL API
- GraphQL API Resources
- API V3 to API V4
- Validate the .gitlab-ci.yml (API)
- User Docs
- Abuse reports
- User account
- Active sessions
- Deleting a User account
- Permissions
- Personal access tokens
- Profile preferences
- Threads
- GitLab and SSH keys
- GitLab integrations
- Git
- GitLab.com settings
- Infrastructure as code with Terraform and GitLab
- GitLab keyboard shortcuts
- GitLab Markdown
- AsciiDoc
- GitLab Notification Emails
- GitLab Quick Actions
- Autocomplete characters
- Reserved project and group names
- Search through GitLab
- Advanced Global Search
- Advanced Syntax Search
- Time Tracking
- GitLab To-Do List
- Administrator Docs
- Reference architectures
- Reference architecture: up to 1,000 users
- Reference architecture: up to 2,000 users
- Reference architecture: up to 3,000 users
- Reference architecture: up to 5,000 users
- Reference architecture: up to 10,000 users
- Reference architecture: up to 25,000 users
- Reference architecture: up to 50,000 users
- Troubleshooting a reference architecture set up
- Working with the bundled Consul service
- Configuring PostgreSQL for scaling
- Configuring GitLab application (Rails)
- Load Balancer for multi-node GitLab
- Configuring a Monitoring node for Scaling and High Availability
- NFS
- Working with the bundled PgBouncer service
- Configuring Redis for scaling
- Configuring Sidekiq
- Admin Area settings
- Continuous Integration and Deployment Admin settings
- Custom instance-level project templates
- Diff limits administration
- Enable and disable GitLab features deployed behind feature flags
- Geo nodes Admin Area
- GitLab Pages administration
- Health Check
- Job logs
- Labels administration
- Log system
- PlantUML & GitLab
- Repository checks
- Repository storage paths
- Repository storage types
- Account and limit settings
- Service templates
- System hooks
- Changing your time zone
- Uploads administration
- Abuse reports
- Activating and deactivating users
- Audit Events
- Blocking and unblocking users
- Broadcast Messages
- Elasticsearch integration
- Gitaly
- Gitaly Cluster
- Gitaly reference
- Monitoring GitLab
- Monitoring GitLab with Prometheus
- Performance Bar
- Usage statistics
- Object Storage
- Performing Operations in GitLab
- Cleaning up stale Redis sessions
- Fast lookup of authorized SSH keys in the database
- Filesystem Performance Benchmarking
- Moving repositories managed by GitLab
- Run multiple Sidekiq processes
- Sidekiq MemoryKiller
- Switching to Puma
- Understanding Unicorn and unicorn-worker-killer
- User lookup via OpenSSH's AuthorizedPrincipalsCommand
- GitLab Package Registry administration
- GitLab Container Registry administration
- Replication (Geo)
- Geo database replication
- Geo with external PostgreSQL instances
- Geo configuration
- Using a Geo Server
- Updating the Geo nodes
- Geo with Object storage
- Docker Registry for a secondary node
- Geo for multiple nodes
- Geo security review (Q&A)
- Location-aware Git remote URL with AWS Route53
- Tuning Geo
- Removing secondary Geo nodes
- Geo data types support
- Geo Frequently Asked Questions
- Geo Troubleshooting
- Geo validation tests
- Disaster Recovery (Geo)
- Disaster recovery for planned failover
- Bring a demoted primary node back online
- Automatic background verification
- Rake tasks
- Back up and restore GitLab
- Clean up
- Namespaces
- Maintenance Rake tasks
- Geo Rake Tasks
- GitHub import
- Import bare repositories
- Integrity check Rake task
- LDAP Rake tasks
- Listing repository directories
- Praefect Rake tasks
- Project import/export administration
- Repository storage Rake tasks
- Generate sample Prometheus data
- Uploads migrate Rake tasks
- Uploads sanitize Rake tasks
- User management
- Webhooks administration
- X.509 signatures
- Server hooks
- Static objects external storage
- Updating GitLab
- GitLab release and maintenance policy
- Security
- Password Storage
- Custom password length limits
- Restrict allowed SSH key technologies and minimum length
- Rate limits
- Webhooks and insecure internal web services
- Information exclusivity
- How to reset your root password
- How to unlock a locked user from the command line
- User File Uploads
- How we manage the TLS protocol CRIME vulnerability
- User email confirmation at sign-up
- Security of running jobs
- Proxying assets
- CI/CD Environment Variables
- Contributor and Development Docs
- Contribute to GitLab
- Community members & roles
- Implement design & UI elements
- Issues workflow
- Merge requests workflow
- Code Review Guidelines
- Style guides
- GitLab Architecture Overview
- CI/CD development documentation
- Database guides
- Database Review Guidelines
- Database Review Guidelines
- Migration Style Guide
- What requires downtime?
- Understanding EXPLAIN plans
- Rake tasks for developers
- Mass inserting Rails models
- GitLab Documentation guidelines
- Documentation Style Guide
- Documentation structure and template
- Documentation process
- Documentation site architecture
- Global navigation
- GitLab Docs monthly release process
- Telemetry Guide
- Usage Ping Guide
- Snowplow Guide
- Experiment Guide
- Feature flags in development of GitLab
- Feature flags process
- Developing with feature flags
- Feature flag controls
- Document features deployed behind feature flags
- Frontend Development Guidelines
- Accessibility & Readability
- Ajax
- Architecture
- Axios
- Design Patterns
- Frontend Development Process
- DropLab
- Emojis
- Filter
- Frontend FAQ
- GraphQL
- Icons and SVG Illustrations
- InputSetter
- Performance
- Principles
- Security
- Tooling
- Vuex
- Vue
- Geo (development)
- Geo self-service framework (alpha)
- Gitaly developers guide
- GitLab development style guides
- API style guide
- Go standards and style guidelines
- GraphQL API style guide
- Guidelines for shell commands in the GitLab codebase
- HTML style guide
- JavaScript style guide
- Migration Style Guide
- Newlines style guide
- Python Development Guidelines
- SCSS style guide
- Shell scripting standards and style guidelines
- Sidekiq debugging
- Sidekiq Style Guide
- SQL Query Guidelines
- Vue.js style guide
- Instrumenting Ruby code
- Testing standards and style guidelines
- Flaky tests
- Frontend testing standards and style guidelines
- GitLab tests in the Continuous Integration (CI) context
- Review Apps
- Smoke Tests
- Testing best practices
- Testing levels
- Testing Rails migrations at GitLab
- Testing Rake tasks
- End-to-end Testing
- Beginner's guide to writing end-to-end tests
- End-to-end testing Best Practices
- Dynamic Element Validation
- Flows in GitLab QA
- Page objects in GitLab QA
- Resource class in GitLab QA
- Style guide for writing end-to-end tests
- Testing with feature flags
- Translate GitLab to your language
- Internationalization for GitLab
- Translating GitLab
- Proofread Translations
- Merging translations from CrowdIn
- Value Stream Analytics development guide
- GitLab subscription
- Activate GitLab EE with a license