Skip to content

docs: clarify relative public_url usage#1073

Draft
leno23 wants to merge 1 commit into
trunk-rs:mainfrom
leno23:hermes-auto/trunk-997-relative-public-url
Draft

docs: clarify relative public_url usage#1073
leno23 wants to merge 1 commit into
trunk-rs:mainfrom
leno23:hermes-auto/trunk-997-relative-public-url

Conversation

@leno23
Copy link
Copy Markdown

@leno23 leno23 commented May 17, 2026

Summary

  • Clarify that build.public_url can be a relative value such as ./.
  • Add a trunk build --release --public-url='./' example for deployments that may be served from different prefixes, including GitLab Pages.
  • Show the equivalent [build] configuration value.

Fixes #997

Test plan

  • git diff --check
  • Source-level docs check confirming the new --public-url='./', public_url = "./", and GitLab Pages guidance are present.
  • mdbook test guide was not run locally because mdbook is not installed in this environment.

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.

CORS errors when deploying to Gitlab Pages

1 participant