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
Currently, the site-prefix configuration option is only used for manually created links, for example in e-mails, but not for internal links and resources (css, images, ...).
This complicates the integration with other applications (e.g. jenkins) on a common host with a web-proxy as entry point as the proxy needs to read the HTML output and rewrite the URLs.
Obeying the site-prefix in all links in the html output produced by package-drone would help here.
Currently, the site-prefix configuration option is only used for manually created links, for example in e-mails, but not for internal links and resources (css, images, ...).
This complicates the integration with other applications (e.g. jenkins) on a common host with a web-proxy as entry point as the proxy needs to read the HTML output and rewrite the URLs.
Obeying the site-prefix in all links in the html output produced by package-drone would help here.
For reference, see also this discussion: https://groups.google.com/forum/#!topic/package-drone/WvGQmgoHgbM
The text was updated successfully, but these errors were encountered: