Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build with relative base URL #84

Merged
merged 1 commit into from
Jun 1, 2024

Conversation

mgoltzsche
Copy link
Contributor

@mgoltzsche mgoltzsche commented May 18, 2024

snapweb was built using the absolute path / as base URL (default), making asset links absolute. However, hard-coding an absolute base path prevents serving snapweb under a different path, e.g. exposing snapweb under /snapcast/ via a reverse-proxy.
To support those kinds of setups, snapweb is built with a relative base URL ./ now.

TL;DR:
In the Makefile-based Snapcast 0.27.0 build I used previously the asset paths were still relative. For me it broke with the update to Snapcast 0.28.0 when using the snapweb v0.7.0 zip distribution explicitly.

snapweb was built using / (absolute path) as base URL.
However, hard-coding an absolute base path prevents serving snapweb under a different path, e.g. exposing snapweb under `/snapcast/` via a reverse-proxy.
To support those kinds of setups, snapweb is built with a relative base URL now.
@badaix badaix merged commit 4106f90 into badaix:develop Jun 1, 2024
1 check passed
@badaix
Copy link
Owner

badaix commented Jun 1, 2024

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants