Skip to content

ci: serve the docs app's static resources in previews (#6669) (CP: v25.3) - #6670

Merged
peholmst merged 1 commit into
v25.3from
cherry-pick-6669-to-v25.3-1794565872463
Nov 13, 2026
Merged

peholmst merged 1 commit into
v25.3from
cherry-pick-6669-to-v25.3-1794565872463

Conversation

@vaadin-bot

Copy link
Copy Markdown
Contributor

No description provided.

## What

`Dockerfile.preview` now copies `src/main/resources/META-INF/resources`
into the static site that the preview serves. The site is copied after
them, so the site's own files win if a path clashes.

## Why

In production and in the dev server, these resources come from the
Spring Boot docs app: requests under `/vaadin/` go to it. Preview
deployments serve only the static DSP output with `serve` and don't run
that app, so every `/vaadin/*` path returns 404. For example, on the
preview of #6668:

| Path | Preview | vaadin.com |
|---|---|---|
| `/vaadin/tutorial/schema.sql` | 404 | 200 |
| `/vaadin/videos/aura-theme-editor-teaser.webm` | 404 | 200 |

That breaks the SQL downloads in the tutorial's setup step and the video
on the Aura theme page in every preview.

The preview is served from the site root, so the copied files land at
the same paths the articles link to.

## Testing

- A minimal Docker build that runs only these two `COPY` lines put the
files at `vaadin/tutorial/*.sql`, `vaadin/videos/*.webm` and `icons/*`,
and a clashing file from the site overrode the resource.
- The full preview build wasn't run locally, as it needs the Pro key.
This PR's own preview deployment is the end-to-end check:
`/vaadin/tutorial/schema.sql` on it should return 200.

Labeled `target/v25.3` because the release branch has the same
`Dockerfile.preview`, so previews of PRs to `v25.3` have the same 404s.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@peholmst
peholmst merged commit 6a0ba56 into v25.3 Nov 13, 2026
9 of 10 checks passed
@peholmst
peholmst deleted the cherry-pick-6669-to-v25.3-1794565872463 branch November 13, 2026 10:38
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