Organisation of a webapp

As a side project, I'm trying to learn to make a web app avoiding JS. I started long ago to write a REST API and it's ready. Now I'm learning Yew for the frontend, and I try to get inspiration from GitHub - saschagrunert/webapp.rs: A web application completely written in Rust. 🌍 on how to organise the project.

The thing I don't like is the use of Makefile, because I don't like them. But it's also true that the backend and the frontend are build differently.

How you guys organise the code of your fullstack Rust web app? And how do you manage the build process?

I use a Makefile.
make
make publish

Alternatively a shell script. Or a Rust program to invoke the actual build…

1 Like

Thank you for your answer :slight_smile: I think I'll try just or mask

I also find cargo-make, cargo-watch and cargo-edit very helpful. Have a look on crates.io. I didn't dive deep into them yet but they add useful cargo commands. I also find microserver to have a tiny rust web server.

2 Likes

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.