Consider switching to tokio/axum/hyper stack about alexandrie HOT 9 CLOSED

I might have a go at it this weekend.

from alexandrie.

Yeah, I'm on board, it would indeed be better organised that way.

from alexandrie.

Just to mention that: We've already done this migration while alexandrie was in a hiatus. If you want to take that as a base, we can provide that code to y'all once gitlab is back up.

from alexandrie.

The migration is now complete and has landed, thank you all for having started this initiative.

@jcgruenhage Thank you for your proposition.
I think writing this migration from scratch has helped me learn the Axum framework in more detail than if I were to use an existing base, which is good to be able to maintain it more effectively later, so I think it worked out for the better that way.

from alexandrie.

If time is an issue here, I'd be willing to help with this.

from alexandrie.

Hi !

While I really like Tide's design as a web framework (from a DX perspective), I completely agree that keeping it has quite a few downsides, in terms of features as you mentioned, and also in terms of compile time and dependency count (due to runtime duplication).

Alexandrie has some dependencies that require running Tokio as a runtime anyway (aws-sdk-s3 for S3 storage and reqwest for external auth), so switching away from Tide would allow to drop async-std and only ship Tokio as the single async runtime.

Also, I was also considering using something like Leptos to allow for a more dynamic frontend for Alexandrie (instead of the .hbs templates, which can be impractical), but this was impossible as of now with Tide, and switching to Axum would make that a possible endeavour.

As you mentioned, I don't think migrating would take that much time and would most likely be a quite straightforward process.
Even session management can be migrated without much trouble, with axum_sessions also being based on async-session, just like tide's sessions.

I think I can get around to it rather soon, but if you wish to have a go at it yourself, I'd be happy to review and accept a PR.

from alexandrie.

A question: as part of this migration, is it alright if I move the repo to workspace dependencies, to make it easier to track things here?

from alexandrie.

You mean extracting declarations of dependencies that are common to multiple crates into the worspace's Cargo.toml ?

from alexandrie.

yes

from alexandrie.