From 0db2f84a221d20deb3723d9259c450f4aeeae957 Mon Sep 17 00:00:00 2001 From: hugocasa Date: Thu, 3 Sep 2026 15:22:27 +0200 Subject: [PATCH] docs: state that relative-url gitlab installs are out of scope Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01C1xHmkxuxYb1GYvth1BS75 --- backend/ee-repo-ref.txt | 2 +- docs/git-sync-gitlab-setup.md | 8 ++++++++ 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/backend/ee-repo-ref.txt b/backend/ee-repo-ref.txt index fc13c028a0..ef5cbb497f 100644 --- a/backend/ee-repo-ref.txt +++ b/backend/ee-repo-ref.txt @@ -1 +1 @@ -1e45435a89736396036e200816d7a73525c67f46 +0dae6fb996c6bf0ffb2f60bfcf9bdda8baca2e85 diff --git a/docs/git-sync-gitlab-setup.md b/docs/git-sync-gitlab-setup.md index 47bc700a65..1bf92b39f4 100644 --- a/docs/git-sync-gitlab-setup.md +++ b/docs/git-sync-gitlab-setup.md @@ -85,6 +85,14 @@ enables *Allow requests to the local network from webhooks and integrations* same private network as GitLab needs this; without it, hook creation fails with a "blocked" error and the repository keeps polling. +**A relative-URL install is not supported.** GitLab can be served under a path +prefix (`https://example.com/gitlab`), and that prefix cannot be told apart from +a group of the same name: `example.com/a/b/c.git` is either group `a/b` project +`c`, or prefix `a` with group `b` project `c`. Windmill reads it as the nested +group, so on a relative-URL install it derives the wrong API base and the managed +features stay unavailable. Such a repository still syncs through its token URL, +which needs no API base. + Everything else is identical: Windmill talks to `/api/v4` and needs no inbound access of its own beyond the hook deliveries.