Did you manage to get any API calls going? I didn't and I was kind of disappointed as it is the first thing I do with any framework - check how ergonomic communication with the backend is

Since it's all wasm for the web, could you use hyper to make calls to the backend?

Looks like it just simply uses reqwest: https://github.com/DioxusLabs/dioxus/blob/master/examples/login_form.rs

That makes sense

I mean I guess in that respect you could still just use hyper

hyper doesn't really work with WASM (since it works on raw transport-layer streams; QUIC/HTTP3 really makes being technically correct a mouthful ), what you probably want is either reqwest (which uses the fetch API under the hood) or gloo-net, which is yet another ergonomic wrapper over the fetch API, but maintained by the WASM working group (probably a lil more lightweight than reqwest, but I haven't tested it yet)

I used gloo-net in my NASA photo fetcher.

Oh nice! Do you have any stats on its binary size?

Ha! No, stuff like that is a bit beyond me at the moment. I also noticed that I'm using gloo_net in the "Yew re-vamp" of the office intranet site I made. I'm going to re-work the NASA photo app using Dioxus, so will look into this binary size stat as I do that.

tbh I think reqwest is really the only viable one at the moment

hyper is just the underlying tech for reqwest, ureq can't use async and I think gloonet looks like it's more for direct wasm stuff

Yeah, reqwest is the only HTTP client I know of that works both on native and on WASM, but, personally, I would write a trait abstraction using the

http

crate types for libraries and for binary projects, well, most binary projects either run on native platforms or in WASM; it's rather rare that you need the compatibility in that area. I think alternative HTTP clients, even if they are built on hyper, too, are important. Each client has its own niche most of the time. reqwest, for example, isn't a client I personally would use to load data from unknown servers (on native platforms that is, on WASM it uses

fetch

which doesn't have this issue), because reqwest doesn't have a way to restrict the body size (https://github.com/seanmonstar/reqwest/issues/1234). That's fine for APIs where you trust the host you are connecting to but for, for example, crawlers? No thanks.

Ah, yeah that's ture

I did't realize all the intricacies of these crates... Thanks for the info!

and there it is peeps every single reason to use rust

Hiya, for my serenity bot I need a little something that runs an async task every so many minutes. Normally I'd do a tokio::spawn, but I can't find anything similar in the shuttle-runtime. Is there a prefered way to achieve this?

tokio::select!()

can do this fairly well - the custom service docs goes over a way you can use it: https://docs.shuttle.rs/tutorials/custom-service

Aye thanks, that's just what I was looking for!

Happy to help

Oh, to make it even easier, doing a tokio::spawn(async move { loop { ... }}), just works fine even after deploying. I thought it wasn't working but that was something else entirely.

Is there a way to deploy my project with the openssl crate? I recently added

openssl = "0.10.52"

to my Cargo.toml so I can use tokio-postgres and postgres-openssl. This works fine when I do cargo shuttle run and host locally but once I deploy I run into websocket errors.

WebSocket errors? As in communication with Shuttle or WebSocket errors from clients to your deployment?

This is the error I'm getting

Maybe try using

cargo shuttle project restart

to restart the container then deploy again

this worked. TY!

No worries, happy to help

Where do I go to if there is an issue with my deployment? My project is stuck in loading state for 12 hours now and I'm unable to access logs or issue a stop or clean command.

Heya, it's normally easiest to open a thread in #1020096112666890321

I dunno if this is the right channel for this, I hacked together support for nuxt in the create-shuttle-app thingy, but its real ugly atm (i just wanted to see if i could make it work, as i, how to put it lightly, prefer working with vue) - how to proceed, is there interest in this? Deployed static nuxt demo app: https://my-app-94f23b.shuttleapp.rs/