shuttle-hq / shuttle

Build & ship backends without writing any infrastructure files.
https://shuttle.rs
Apache License 2.0
6.05k stars 251 forks source link

Support Yew #1113

Closed mattheworris closed 1 year ago

mattheworris commented 1 year ago

Yew seems to be a popular front-end framework, it would be great to support it along side the other front-end options.

jonaro00 commented 1 year ago

Hi Matthew,

Shuttle currently supports any front-end that compiles to static assets. Trunk can compile Yew to such assets, and then you can use shuttle-static-folder to serve them. The catch is that the building of the front-end assets now needs to be done before you deploy, but we are aiming to support more ways of building them at deploy time (such as Trunk).

There is no official example for how to set up a project with Yew yet, but there are some community efforts. This is an example of a fullstack setup: https://github.com/TylerBloom/shuttle-fullstack-rust-example

jonaro00 commented 1 year ago

Another alternative: https://github.com/sentinel1909/shuttle-template-yew

sentinel1909 commented 1 year ago

Another alternative: https://github.com/sentinel1909/shuttle-template-yew

I just pushed up what I think of as a reasonably complete MVP for this template. It seems to work nicely.

mattheworris commented 1 year ago

Excellent, thank you.

On Thu, Aug 3, 2023 at 12:29 AM Jeff Mitchell @.***> wrote:

Another alternative: https://github.com/sentinel1909/shuttle-template-yew

I just pushed up what I think of as a reasonably complete MVP for this template. It seems to work nicely.

— Reply to this email directly, view it on GitHub https://github.com/shuttle-hq/shuttle/issues/1113#issuecomment-1663272941, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALGDXGSUY45T23L2FAERQTXTMSI5ANCNFSM6AAAAAA22YRFHE . You are receiving this because you authored the thread.Message ID: @.***>

sentinel1909 commented 1 year ago

Thinking this issue can be closed? I'm continuing to focus on using Yew as my frontend web framework of choice, so can take responsibility for it from a documentation/learning resources perspective.

jonaro00 commented 1 year ago

There is more to build in regards to this, but the main point of this issue is addressed. Closing