The recently-released axum 0.8.3 brought some small changes that should reduce compile times for downstream projects. Curious whether it's noticable for anybody!
Also, the next release is likely to include some further improvements like that: https://github.com/tokio-rs/axum/pull/3300
Does there already exist an Extractor for Axum that answers the question "what language(s) does the user prefer" in the form of a list made up of standardized language enums?
I couldn't find one, so I ended up writing one. I can see about publishing the crate if anyone's interested.
Ever wondered how to do Dependency Injection in a rigid statically typed language like Rust? Learn how #Bevy and #Axum do it in this excellent tutorial: https://promethia-27.github.io/dependency_injection_like_bevy_from_scratch/ #rustlang #gamedev 
Any advice on choice of #Rust web #backend #framework?
I'm considering #Actix and #Axum, and like the look of #Salvo but am new to this so any comments from experience would be helpful.
I'll be creating a localhost API server which will wrap my #RustLang lib and give local apps a way to talk to a p2p storage system. So a custom API for some things, one for #rclone, possibly #WebDAV.
Thoughts?
Published my first crate to crates.io recently. Nothing fancy, a simple #Axum layer for caching HTTP responses – with the option to reuse a stale response in case of failure to produce a new successful one – written for a project at work. Maybe someone else will find it useful. :)
https://crates.io/crates/axum-response-cache
(I’ve been doing Rust for years, a bit ashamed I’d never published any open crate before; even if I’ve some small contributions to other projects)
Is there any disadvantage when using OnceCell from #tokio (https://docs.rs/tokio/latest/tokio/sync/struct.OnceCell.html) for the state (DBs, etc) instead of the state management directly provided by #axum ?
The more Rust I write, the more I like it. I just need more places to use it. I'm not going to introduce it at work (trust me) and I just don't do that many personal projects.
I wonder if people would like a set of tutorials on, like, "#Axum for #Django engineers" or "#Rocket for #Djangonauts" would be useful to folks?
UPDATE: I’ve just discovered that axum_extra (https://docs.rs/axum-extra/latest/axum_extra/extract/struct.Form.html) has its own `Form` type which does use serde_html_form underneath and supports optional values and sequences. So not all hope is lost! The fix is simple (change the Form type used), but for better discoverability #axum’s own type’s documentation could mention the limitations and link to the alternative.
Form data (x-www-form-urlencoded) support in #Axum is a bit disappointing. It uses #serde’s serde_urlencoded underneath, which in principle is fine. But the problem is that HTML forms don’t let you *not send* a value, which makes the whole thing useless with optional fields. You can set a field in a form to not be required and send an empty value (`?foo&bar=3&…` or `?foo=&bar=3&…` for empty `foo`) but then serde treats it as a present empty string and fails deserialization.
@mo8it I really enjoy using axum-ctx, thanks for the crate! :)
I’ve a thought though:
User-facing `Message` is always sent as text/plain.
I see the `RespErr` has support for custom Response variant, but there’s no way to provide one for an existing error: `.user_msg()` only accepts Into<Message>.
What’d’you think of adding eg. `.response(IntoResponse)`?
Would make it easier to provide custom HTML error views (old-school MPAs; #htmx based services; custom JSON error APIs, &c.)
Announcing axum-ctx: #Axum error handling library inspired by anyhow 
Documentation with examples 
https://docs.rs/axum-ctx
The first screenshot shows the code without `axum-ctx`, the second one with it 
It lets you write concise "one-liners". Any chaining fans here? 
I will write a blog post about it. But first, I would like to get some feedback here 
Why is it so fun to create APIs? Something about it is so oddly satisfying, the image down below is part of my API documentation and its just pure dopamine to look at xD I could do this kind of stuff forever… #api #rustlang #axum #programming #technology #coding #dev #development
Does anyone have experience using #RustLang and #axum for APIs? I wanted to make a little messenger API as my first lil rust project, I'm wondering if there's tips for improvements you might want to share :) I don't wanna get used to doing sub-optimal things from the start (●__●) It's in the early stages but the rough structure is pretty much clear.
That's the repo:
https://github.com/Zitronenjoghurt/lemcom-api
I'll appreciate any feedback c:
Made my first #htmx #rust app today on #shuttle. Still very WIP, but without prior #axum or #htmx experience setup was buttery smooth.
src: https://github.com/dsmiller95/fraculation-leaderboard
site: https://fraculation-leaderboard.shuttleapp.rs/leaderboard
Reduce complexity for #RustLang backend development 
Let people write weird Rust code using macros generating more code in a crate that is fed to a custom transpiler that generates multiple Rust crates that you are supposed to then build and use in production 
On top of that, you introduce weird licensing so that teams need an activation key with a MONTHLY FEE 
Thanks #Pavex… 
Rustaceans, just use #Axum 
My dive into #Rust and its web ecosystem continues. This time, I'm using #Axum to serve HTML from an endpoint and sending static files from a directory.
The IDE I'm using is #JetBrains #RustRover.
Note: Cool features from RustRover include automatic dependency refresh, HTML Language injection, and a built-in browser in the IDE (via plug-in), not to mention really good language support.
#OxiTraffic, a self-hosted, simple and privacy respecting website traffic tracker 
I just published version 0.6 with a #Docker image! 
(You don't have to use Docker though)
Do you have a #blog?
I can host it for you if you want to test it with your website 
Of course, it is written in #Rust
Check out the README, I spent a lot of time on it 
https://codeberg.org/mo8it/oxitraffic
Boost? 
