-
Hi ! I’m still new to Dioxus, didn’t had the time to build big things, but so far so good, and I’m loving this framework. However, I couldn’t find documentation on how to build a server binary that :
Currently all I can do is separate functions that do separate stuff and never interact with each other, except through file manipulations, but I’m not sure this is very async-friendly). My end goal is to have, for example, and app that continuously fetches and sends data from and to another server, and when asked (through API requests), can sum up the exchanged data (and obviously serve the web app too). My main question is : How to structure the codebase the Dioxus way ? (all in one codebase) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
You can start from https://github.com/DioxusLabs/dioxus/tree/main/examples/fullstack-auth/src or workspace template from dioxus. Seperate the server side like on the fullstack-auth example. For workers i would suggest using https://github.com/geofmureithi/apalis as it also have web dashboard and one example for axum integration. |
Beta Was this translation helpful? Give feedback.
You can start from https://github.com/DioxusLabs/dioxus/tree/main/examples/fullstack-auth/src or workspace template from dioxus. Seperate the server side like on the fullstack-auth example. For workers i would suggest using https://github.com/geofmureithi/apalis as it also have web dashboard and one example for axum integration.