You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can see the original issue made on my TurboWarp Docker project here for additional context on why this issue was made, or if I did not properly explain something in this issue.
The production build of the extension gallery website currently generates extension, documentation, and sample URLs with https://extensions.turbowarp.org/, which is hard-coded. For DX, you could make the deployment origin configurable instead of hard-coded.
Possible Solution
Here is how you could solve this issue:
The default remains https://extensions.turbowarp.org/.
The production build uses the configured origin for generated gallery pages, extension URLs, documentation URLs, sample URLs, and sitemap URLs.
The build rewrites only generated output when necessary. It should not require contributors to change every source URL.
The deployment origin must use https: in production.
The build normalizes the origin so it has one trailing /.
Note
You can see the original issue made on my TurboWarp Docker project here for additional context on why this issue was made, or if I did not properly explain something in this issue.
The production build of the extension gallery website currently generates extension, documentation, and sample URLs with
https://extensions.turbowarp.org/, which is hard-coded. For DX, you could make the deployment origin configurable instead of hard-coded.Possible Solution
Here is how you could solve this issue:
https://extensions.turbowarp.org/.https:in production./.