Serve static directories, files, and RustEmbed assets in Salvo apps.
npx skills add https://github.com/salvo-rs/salvo-skills --skill salvo-static-files
Please help me install this Agent Skill. Skill: salvo-static-files Source: https://github.com/salvo-rs/salvo-skills/tree/main/skills/salvo-static-files Command: npx skills add https://github.com/salvo-rs/salvo-skills --skill salvo-static-files
Serving static files and embedded assets is a common requirement for web apps, but configuring routes, defaults, caching, and SPA fallbacks can be error-prone when using a framework like Salvo.
Set up a Salvo app to serve static files from a directory with a default file and optional directory listing.
High-intent search queries and answers about installing and using this skill.
To serve static files in a Salvo web application, you route requests using StaticDir or StaticFile components. This allows you to map directories, single files, and assets directly to HTTP endpoints with configurable defaults and directory listings.
Yes, you can embed static assets for a single-binary deployment in Salvo using RustEmbed support. This bundles your CSS, JS, and images directly into the compiled executable, eliminating external file dependencies at runtime.
Configuring SPA fallbacks for static assets involves routing unknown paths to a default index file. Salvo supports SPA-friendly fallbacks, ensuring client-side routing works correctly by serving the entry point for unmatched routes.
Yes, Salvo supports optional directory listing and default files when serving static directories. You can configure these options to automatically display folder contents or serve a specified default file for directory requests.
You set cache-control headers for static files in Salvo using configurable cache options. This enables production-ready HTTP caching, reducing bandwidth and improving load times for static assets like CSS and JavaScript.
Embedded assets bundle files into the binary via RustEmbed, providing a self-contained executable for deployment without external file dependencies. Serving from a directory reads files at runtime, which is easier for development but requires managing file paths in production.
rodydavisGenerate multi-page static sites from Markdown files with file-based routing.
aalmadaDiagnose HybridCache and Redis caching issues in .NET applications.
tdcareCompress HTTP responses in Salvo web services with gzip, brotli, zstd, or deflate.
cevioIntegrate Next.js rendering and API controllers into a Koa HTTP service.
