redoal/questions
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Pin portal v0.3.1 - content-hashed assets (LEPTOS_HASH_FILES=true)
Deploy instance / deploy (push) Successful in 0s
Details
Lint and reload / lint (push) Successful in 2s
Details
Lint and reload / reload (push) Successful in 1s
Details

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Bendik Aagaard Lynghaug
2026-08-25 19:51:30 +02:00
co-authored by Claude Fable 5
parent 9a5ebb6715
commit 83f7533c21
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/deploy.yml
+5 -1
View File
@@ -18,7 +18,7 @@ on:
- .gitea/workflows/deploy.yml - .gitea/workflows/deploy.yml
env: env:
PORTAL_RELEASE: v0.3.0 PORTAL_RELEASE: v0.3.1
INSTANCE: redoal-portal INSTANCE: redoal-portal
jobs: jobs:
@@ -67,6 +67,10 @@ jobs:
# The release tarball carries the site bundle at site/ (no # The release tarball carries the site bundle at site/ (no
# target/ prefix), so override Cargo.toml's build-time path. # target/ prefix), so override Cargo.toml's build-time path.
LEPTOS_SITE_ROOT=site LEPTOS_SITE_ROOT=site
# Portal ships content-hashed pkg files (portal.<hash>.js) with
# a hash.txt in the site root; this makes the server reference
# them, so a stale cached bundle can never pair with new wasm.
LEPTOS_HASH_FILES=true
# Read-only Gitea token - here it also backs the # Read-only Gitea token - here it also backs the
# gitea_releases source for the private redoal/redoal repo, # gitea_releases source for the private redoal/redoal repo,
# so the owning user needs read access there. # so the owning user needs read access there.