Verso

alois/Verso

Fork 0

Files

T

History

claudeandClaude Sonnet 4.6 eb74c4fced

Build and Deploy Verso / deploy (push) Successful in 4m19s

Details

Build and Deploy Verso (prod) / deploy (push) Successful in 1m7s

Details

fix(nginx): route all build output files directly to clsi-nginx

Previously only output.* (output.html, output.pdf, etc.) bypassed the
web server. Companion assets (CSS, JS, images, videos, fonts) from
Quarto/RevealJS presentations went through the web server, hitting the
miscOutputDownload rate limiter (1000 req/hour per project). A heavy
presentation loads 50+ assets per page view and would exhaust the limit
quickly, returning 429 for most assets and leaving the page unstyled.

The build ID is an unguessable random token — the same security model
already used for output.html being served without auth. Routing all
output files through clsi-nginx is safe and also fixes Content-Type
for media files (video/mp4 etc.) now that the mime type fix is in place.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-07-14 11:02:50 +00:00

bin

[server-ce] run node scripts as www-data user (#27504 )

2025-07-31 08:05:15 +00:00

config

feat: add pragmatic git sync — push project to external git remote

2026-06-23 20:01:16 +00:00

cron

[server-ce] run node scripts as www-data user (#27504 )

2025-07-31 08:05:15 +00:00

hotfix

[filestore] add pdftocairo conversion option (#31627 )