Merge pull request #395 from fairuzrahman/patch-1

Author: Cinzya

.github/workflows/claude-code-review.yml

@@ -12,6 +12,7 @@ on:
 
 jobs:
   claude-review:
+    if: false
     # Optional: Filter by PR author
     # if: |
     #   github.event.pull_request.user.login == 'external-contributor' ||

conductor.json

@@ -0,0 +1,6 @@
+{
+  "scripts": {
+    "run": "bun install && bun run dev"
+  },
+  "runScriptMode": "nonconcurrent"
+}

docs/knowledge-base/git/gitlab/integration.md

@@ -1,9 +1,10 @@
 ---
 title: "Integration"
-description: "Connect GitLab repositories to Coolify with deploy keys, automatic webhooks, and merge request deployments for CI/CD automation"
+description: "Connect GitLab repositories to Coolify with deploy keys, Gitlab container registry with deploy token, automatic webhooks, and merge request deployments for CI/CD automation"
 ---
 
 # GitLab Integration
+
 ## Public Repositories
 
 You can use public repositories without any additional setup.
@@ -24,14 +25,15 @@ Private repositories require a few more steps to setup.
 1. Add a private key (aka `Deploy Keys`) to Coolify and to your GitLab repository in the `Settings` / `Repository` / `Deploy Keys` menu.
 
 ::: warning Caution
-  - You can generate a new key pair with the following command: 
-  
-  ```bash
-  ssh-keygen -t rsa -b 4096 -C "deploy_key" 
-  ```
 
-  - Or you can also use Coolify to generate a new key for you in the `Keys & Tokens` menu.
-:::
+- You can generate a new key pair with the following command:
+
+```bash
+ssh-keygen -t rsa -b 4096 -C "deploy_key"
+```
+
+- Or you can also use Coolify to generate a new key for you in the `Keys & Tokens` menu.
+  :::
 
 2. Create a new resource and select the `Private Repository (with deploy key)`
 3. Add your repository URL to the input field, for example: `[email protected]:andrasbacsai/coolify-examples.git`
@@ -42,6 +44,31 @@ You need to use the SSH URL, so the one that starts with `git@`.
 
 4. That's it! Coolify will automatically pull the latest version of your repository and deploy it.
 
+## Public Container Registry
+
+You can use public container registry without any additional setup.
+
+1. Select the `Docker Image` option in the Coolify when you create a new resource.
+2. Add your public container registry URL and also the tag to the input field, for example: `registry.gitlab.com/username/repository:latest`.
+3. Press the `Deploy` button.
+4. That's it! Coolify will automatically pull the latest version of your container registry and deploy it.
+
+## Private Container Registry
+
+Private container registry require a few more steps to setup.
+
+1. Add a `Deploy Token` in your GitLab repository in the `Settings` / `Repository` / `Deploy Token` with scope `read_registry`. This step will generate credentials `username` and `token`
+2. login docker with that credentials in your coolify server
+
+```
+echo "token-xxx" | docker login registry.privategitlab.com -u gitlab+deploy-token-xxx --password-stdin
+```
+
+3. Select the `Docker Image` option in the Coolify when you create a new resource.
+4. Add your private container registry URL and also the tag to the input field, for example: `registry.privategitlab.com/username/repository:latest`.
+5. Press the `Deploy` button.
+6. That's it! Coolify will automatically pull the latest version of your container registry and deploy it.
+
 ## Automatic commit deployments with webhooks (Optional)
 
 You can add a custom webhook URL to your GitLab repository to trigger a new deployment when you push to your repository.
@@ -66,4 +93,4 @@ You can add a custom webhook URL to your GitLab repository to trigger a new depl
 This can be set on either public or private repositories.
 :::
 
-The process is the same as the previous one, but you need to select the `Merge request events` option in the `Settings` / `Webhooks` menu.
+The process is the same as the previous one, but you need to select the `Merge request events` option in the `Settings` / `Webhooks` menu.