Skip to content

docs: clarify relative public_url usage #1073

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.

Sign up for GitHub

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

Draft
leno23 wants to merge 1 commit into
base: main
Choose a base branch
from
+9 −0
Draft

docs: clarify relative public_url usage #1073

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions guide/src/configuration/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,6 +131,15 @@ minify = "never" # Control minification: can be one of: never, on_rel
no_sri = false # Allow disabling sub-resource integrity (SRI)
```


`public_url` may be an absolute path such as `/my-app/` or a relative path such as `./`. Use a relative value when the same build output can be served from different prefixes, for example GitLab Pages projects that may be hosted either at a project subpath or at a dedicated domain:

```sh
trunk build --release --public-url='./'
```

The equivalent configuration value is `public_url = "./"` in the `[build]` section.

## Watch section

Trunk has built-in support for watching for source file changes, which triggers
Expand Down