Summary
Make the GUI extension library use a self-hosted extensions gallery instead of the fixed upstream https://extensions.turbowarp.org/ endpoint.
Rationale
The extensions container in this repository is not used by a self-hosted GUI while the GUI hardcodes the upstream gallery URL. Gallery metadata, extension files, icons, documentation, and samples continue to load from the upstream service.
Affected area
gui/src/containers/extension-library.jsx- The
gui/src upstream submodule or a maintained fork/patch layer
Required changes
Add a supported build-time or runtime configuration option for the extensions gallery base URL. Configure the Docker image to use the self-hosted extensions service. Keep the current upstream URL as the default when no override is configured.
Acceptance criteria
- A deployment can set the extensions gallery base URL without editing built application output.
- The GUI requests gallery metadata, extension files, icons, documentation, and samples from the configured self-hosted URL.
- The default configuration preserves existing upstream behavior.
- Documentation describes the configuration and Docker Compose usage.
Backlinks
Summary
Make the GUI extension library use a self-hosted extensions gallery instead of the fixed upstream
https://extensions.turbowarp.org/endpoint.Rationale
The
extensionscontainer in this repository is not used by a self-hosted GUI while the GUI hardcodes the upstream gallery URL. Gallery metadata, extension files, icons, documentation, and samples continue to load from the upstream service.Affected area
gui/src/containers/extension-library.jsxgui/srcupstream submodule or a maintained fork/patch layerRequired changes
Add a supported build-time or runtime configuration option for the extensions gallery base URL. Configure the Docker image to use the self-hosted extensions service. Keep the current upstream URL as the default when no override is configured.
Acceptance criteria
Backlinks