Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I read through the trunk docs and there isn't any explicit reference to using it within a cargo workspace, however trunk includes a few clever features I discovered reading its example config file... So my thinking now is that I will put Trunk.toml in the project root, add index.html to the /client/ directory and point trunk at it, put the trunk output into /dist/
I have a project I've been working on which uses cargo-make to run both the backend and frontend at the same time. The backend is an axum web server, and the frontend uses yew. The frontend builds to a /dist directory which is served by the backend alongside the API. Feel free to steal the structure if you like and adapt it to your needs.
Related posts
- Why Is the Front End Stack So Complicated?
- Awesome presentation of Dioxus - cross-platform GUI framework at RustNL
- Helper/cheat tool for the board game Cryptid - my first website built with Rust/Wasm
- Is rust + yew a good starting point for learning web dev?
- Trunk - Build, bundle & ship your rust wasm application to the web.