Msingi wa maarifa
Tengeneza token ya ufikiaji ya kibinafsi ya GitLab yenye maeneo ya api na write_repository kisha uiunganishe, ili usukumaji (push) utumie tovuti yako.
Connecting GitLab lets a site deploy from one of your GitLab repositories, and lets us publish to GitLab Pages on your account where you choose it as a site's host.
A GitLab account with access to the projects you want to deploy.
In GitLab, select your avatar at the top right, then Edit profile → Access → Personal access tokens, and generate a new token (GitLab may label this Legacy token in the Generate token menu). Name it, set an expiration date, and tick these scopes:
Press Generate token and copy it — GitLab shows it once.
Open Integrations in your dashboard and choose Connect an account. Pick Code hosting as the group and GitLab as the account, fill in API token, and press Connect account.
We test what you paste before anything is saved. A key that does not work is never stored, and the answer says what was wrong with it. A key that works is kept encrypted in our secrets vault — never in our database — and is never shown again, not even to you.
site's repository connection, pick the repository and branch, and a push deploys.
live site.
source of the site's code.
It worked and then stopped. GitLab tokens always expire — usually at most a year after you create them — and GitLab emails you before they do. Create a new one and connect it.
A scope is missing. A token's scopes cannot be changed after it is created; create a new token with both scopes ticked.
It says the key was rejected. Almost always one of three things: a space or a line break copied with it, a key that has expired, or a key that was revoked or regenerated after you copied it. Create a fresh one and paste it again.
It connects, but something later fails. The key authenticates but lacks a permission the action needs. Create a new key with the permissions listed above, then disconnect the old connection and connect the new key.
Open Integrations, find the account and press Disconnect. That deletes the stored key at once. Anything that was using it stops at its next action, and the screens that depended on it say so rather than failing quietly.
Disconnecting does not undo what was already done — records, deployments or settings we changed on your account stay as they are. If you think the key itself may have leaked, also revoke it at the vendor; disconnecting removes our copy, not theirs.
Mambo ambayo tumekuwa tukiandika kuyahusu upangishaji, SEO na kuendesha tovuti kwa kiwango kikubwa.
Jinsi hosting inavyoathiri uwekaji faharasa na usawa wa viungo mwaka 2026: kuweka kurasa kwenye faharasa, kukagua vikoa vya zamani kabla ya kuvijenga, ujenzi wa viungo bila alama, na mtazamo wa ukweli kuhusu kile ambacho miundombinu inaweza na haiwezi kufanya kwa ajili ya SEO.
Soma chapisho →Orodha ya vitendo vya kuaminika kwa ajili ya WordPress ya haraka na salama: kache ya kiwango cha seva, kache ya vitu kwa kila tovuti, idadi ndogo ya programu-jalizi zinazofaa kutumika, kuweka mfumo wa sasa, na kurasa za WooCommerce ambazo hupaswi kuzifanyia kache kamwe.
Soma chapisho →Kile kinachotofautisha mwenyeji unaosimamiwa vizuri na seva ya bei rahisi yenye paneli ya udhibiti — wahamiaji, nakala rudufu, utengaji, akiba halisi na upanuzi wa kweli — na jinsi ya kukitathmini kabla ya kujitolea.
Soma chapisho →Usaidizi umejumuishwa kwenye kila mpango, huduma ya msaada iko wazi saa 24 kwa siku, na unaweza kutuandikia kwa lugha yoyote kati ya lugha zetu 58 — tunakujibu kwa lugha yako.
Wasiliana na usaidizi → Makala zote →