Make the extensions gallery deployment origin configurable

[coderabbitai]

Summary

Make the deployment origin for the self-hosted extensions gallery configurable.

The pinned extensions/src upstream production build currently generates extension, documentation, and sample URLs with https://extensions.turbowarp.org/. The Dockerfile alone cannot change this behavior.

Rationale

A self-hosted gallery must keep gallery links on its configured deployment origin. Links to the upstream service can give users inconsistent content and navigation.

Affected area

• Upstream turbowarp/extensions production build configuration
• The extensions/src submodule integration in this repository

Required changes

Provide an upstream configuration option, maintain a patch, or use a fork so the production build receives a deployment origin. Relative URLs are also acceptable where they preserve existing production behavior.

Acceptance criteria

• The build supports a configurable deployment origin, or generates suitable relative links.
• Generated extension, documentation, and sample URLs use the configured origin or relative links.
• The default upstream production behavior remains unchanged when no self-hosted origin is configured.

Backlinks

• Pull request: feat: initialize repository #1
• Review comment: feat: initialize repository #1 (comment)
• Requested by: @boswellfox

[boswellfox]

@coderabbitai Do you think this should block #1's merge?

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="boswellfox/turbowarp-docker"

echo "== Issue `#2` =="
gh issue view 2 --repo "$repo" --comments

echo
echo "== Pull request `#1` =="
gh pr view 1 --repo "$repo" --comments

echo
echo "== Pull request `#1` changed files =="
gh pr diff 1 --repo "$repo" --name-only

echo
echo "== Pull request `#1` review threads =="
gh api "repos/$repo/pulls/1/comments?per_page=100" \
  --jq '.[] | {path, line, original_line, body, user: .user.login, created_at}'

Length of output: 68039

---

@boswellfox, no. Issue #2 should not block #1 by itself.

The underlying extensions URL limitation needs a follow-up. It requires an upstream change, a maintained patch, or a fork of extensions/src.

It should block #1 only if #1 promises a fully self-hosted extensions gallery where all extension, documentation, and sample links must remain on the deployed origin. Otherwise, merge #1 with the limitation documented and track the follow-up separately.

_{You are interacting with an AI system.}

[boswellfox]

@coderabbitai Do you think I should make a fork of the extension gallery to allow #1 to be merged, or attempt to have this merged upstream with another issue? If you think I should fork it, how do you think I should go about doing it?

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="boswellfox/turbowarp-docker"

echo "== GitHub issue `#2` =="
gh issue view 2 --repo "$repo" --json number,title,body,url,comments \
  --jq '{number,title,body,url,comments: [.comments[] | {author: .author.login, body, url}]}'

echo
echo "== Pull request `#1` =="
gh pr view 1 --repo "$repo" --json number,title,body,url,files \
  --jq '{number,title,body,url,files: [.files[] | {path, additions, deletions}]}'

echo
echo "== Repository file map =="
fd -H -t f -E .git | sort | sed -n '1,300p'

echo
echo "== Gallery and URL references =="
rg -n -i -C 3 \
  '(extension.?gallery|extensions/src|extensions\.turbowarp\.org|turbowarp\.org/extensions|gallery.*url|base.?url)' \
  . -g '!**/.git/**' || true

Length of output: 10770

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="boswellfox/turbowarp-docker"

echo "== .gitmodules in pull request `#1` =="
gh pr diff 1 --repo "$repo" -- .gitmodules

echo
echo "== Extensions Dockerfile in pull request `#1` =="
gh pr diff 1 --repo "$repo" -- extensions/Dockerfile extensions/nginx.conf compose.yml README.md

echo
echo "== Upstream repository metadata =="
gh repo view TurboWarp/extensions \
  --json nameWithOwner,defaultBranchRef,url,description,licenseInfo \
  --jq '{nameWithOwner,url,description,defaultBranch: .defaultBranchRef.name,license: .licenseInfo.spdxId}'

echo
echo "== Upstream source paths likely to create gallery URLs =="
gh api "repos/TurboWarp/extensions/git/trees/master?recursive=1" --paginate \
  --jq '.tree[]
    | select(.type == "blob")
    | select(.path | test("(src|webpack|vite|config|package\\.json|README)"))
    | .path' \
  | sed -n '1,500p'

Length of output: 1262

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="boswellfox/turbowarp-docker"

echo "== Selected pull request `#1` files =="
gh api "repos/$repo/pulls/1/files?per_page=100" --paginate \
  --jq '.[]
    | select(.filename == ".gitmodules"
          or .filename == "extensions/Dockerfile"
          or .filename == "extensions/nginx.conf"
          or .filename == "compose.yml"
          or .filename == "README.md")
    | {filename, patch}'

echo
echo "== Upstream repository metadata =="
default_branch=$(gh api repos/TurboWarp/extensions --jq '.default_branch')
gh api repos/TurboWarp/extensions \
  --jq '{full_name,html_url,description,default_branch,license: .license.spdx_id}'
printf 'Resolved default branch: %s\n' "$default_branch"

echo
echo "== Upstream source paths =="
gh api "repos/TurboWarp/extensions/git/trees/$default_branch?recursive=1" \
  --jq '.tree[]
    | select(.type == "blob")
    | select(.path | test("(^|/)(src/|package\\.json$|webpack|vite|config|README)"))
    | .path' \
  | sed -n '1,500p'

Length of output: 7147

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

upstream="TurboWarp/extensions"
branch=$(gh api "repos/$upstream" --jq '.default_branch')
tree_file=$(mktemp)
trap 'rm -f "$tree_file"' EXIT

gh api "repos/$upstream/git/trees/$branch?recursive=1" \
  --jq '.tree[] | select(.type == "blob") | .path' > "$tree_file"

echo "== Upstream file map =="
sed -n '1,500p' "$tree_file"

echo
echo "== Files containing the upstream production origin =="
while IFS= read -r path; do
  case "$path" in
    *.js|*.mjs|*.cjs|*.json|*.html|*.md|*.yml|*.yaml|*.ts|*.tsx|*.jsx)
      content=$(gh api "repos/$upstream/contents/$path?ref=$branch" \
        --jq '.content' 2>/dev/null | base64 --decode 2>/dev/null || true)
      if printf '%s' "$content" | grep -q 'https://extensions\.turbowarp\.org'; then
        printf '\n--- %s ---\n' "$path"
        printf '%s\n' "$content" | grep -n -C 4 'https://extensions\.turbowarp\.org'
      fi
      ;;
  esac
done < "$tree_file"

echo
echo "== Build configuration =="
for path in package.json website/package.json website/webpack.config.js website/vite.config.js; do
  if grep -qxF "$path" "$tree_file"; then
    printf '\n--- %s ---\n' "$path"
    gh api "repos/$upstream/contents/$path?ref=$branch" --jq '.content' \
      | base64 --decode
  fi
done

Length of output: 40844

---

@boswellfox, attempt an upstream change first. Do not make a permanent fork before you know the upstream response.

This should not block #1. The README should state that the initial extensions image serves the upstream gallery build and that some gallery URLs still target https://extensions.turbowarp.org/.

An upstream change has the best maintenance cost. The problem is in the upstream source, not in nginx or Docker:

• development/builder.js sets the production host to https://extensions.turbowarp.org/.
• It also uses that host for sitemap entries and sample URL validation.
• Many extension and documentation files contain the same absolute origin.
• extensions/Dockerfile has no build-time origin setting.

Open an upstream issue first. Request a build-time DEPLOYMENT_ORIGIN option, with this behavior:

1. The default remains https://extensions.turbowarp.org/.
2. The production build uses the configured origin for generated gallery pages, extension URLs, documentation URLs, sample URLs, and sitemap URLs.
3. The build rewrites only generated output when necessary. It should not require contributors to change every source URL.
4. The deployment origin must use https: in production.
5. The build normalizes the origin so it has one trailing /.

A relative-URL solution is also good where the consuming API accepts relative URLs. Do not use relative URLs for fields that TurboWarp expects to be absolute URLs, such as docsURI, unless upstream confirms support.

If upstream accepts the design, prepare a small pull request there. Then update the Docker image after the upstream change is released.

If upstream declines the change, or you need this feature before upstream can review it, use a temporary fork. I recommend this fork structure:

1. Fork TurboWarp/extensions under your GitHub account.
2. Create a narrow branch, such as self-hosted-origin.
3. Add one build-time origin setting in the gallery builder.
4. Preserve the existing upstream origin as the default.
5. Update the production build to rewrite the generated gallery files consistently.
6. Add tests that verify the default build retains https://extensions.turbowarp.org/ and a configured build contains only the configured origin for gallery-owned URLs.
7. Change the extensions/src submodule URL to your fork and pin it to a specific commit.
8. Add an automated upstream-sync process. Keep local commits limited to the deployment-origin patch.
9. Document the fork, pinned commit, sync procedure, and license obligations in this repository.

For the Docker integration, expose the setting explicitly:

ARG EXTENSIONS_ORIGIN=https://extensions.turbowarp.org/
ENV EXTENSIONS_ORIGIN=$EXTENSIONS_ORIGIN

RUN npm ci && npm run build

Then build with:

docker build \
  --build-arg EXTENSIONS_ORIGIN=https://extensions.example.com/ \
  -t turbowarp-extensions \
  ./extensions

The upstream builder must read EXTENSIONS_ORIGIN. nginx cannot reliably fix this after the build because URLs also exist inside copied extension JavaScript and generated documentation.

I recommend this decision rule:

• No strict same-origin requirement: merge #1 now and track #2 separately.
• Strict same-origin requirement with normal delivery timing: open the upstream issue and contribute the change upstream.
• Strict same-origin requirement with urgent delivery timing: create a minimal temporary fork while keeping the upstream issue active.

_{You are interacting with an AI system.}

[boswellfox]

@coderabbitai The issue on TurboWarp/extensions has been made.. I will give you updates if anything new happens regarding the new issue.

[coderabbitai]

@boswellfox, thanks for opening TurboWarp/extensions#2655.

This is the preferred first step. Keep #1 independent unless self-hosted same-origin links are a release requirement. If upstream accepts the change, use the upstream implementation in the extensions image. If upstream declines it or the response blocks delivery, use a small temporary fork with only the deployment-origin patch.

🐇

_{You are interacting with an AI system.}