notify VS axum

To support hot reloading, the asset manager definitely has to have some watcher thread, but I have that part dealt with already since I have decided to utilize notify. The other half is to find a way to reload all assets that have changes as determined by the watcher thread. What I am not sure about is how to implement this in a Rustic fashion and with clean architecture while also considering the fact that asset pointers may be held by other objects (such as an object representing an OpenGL program object).

It is a great question. We have based the development on a library called notify, kudos to https://github.com/notify-rs/notify. This library adds a layer of abstraction to each system. It implements kernel-specific hooks as you mentioned. In some cases like Audit extended data, we have developed an integration that detects changes on the Audit log file and processes the given information including a lot of information into Linux systems. We have plans to include it in Windows as well.

In order to detect files changes, we use hotwatch, a simple wrapper over notify that will allow us to save a few lines.

The notify crate uses the inotify API on Linux. However, it's probably not what you want, since one of its limitations is:

If you want to build this yourself, you'll want to build on something like notify - there are libraries like linemux built on top of it that will do a lot of this for you too.

Hey rust community, I'm currently writing a small app using Tokio, but running into a problem when trying to add a file watcher to it. I looked into available crates and found https://github.com/notify-rs/notify to be a good option, though it only exposes a sync interface.

I'm most well versed in Python so I started with that and eventually ended up with a POC using watchdog, but the program took more than a day and a half to traverse everything and register all of the watches. I've been trying to learn Rust for a while, and decided to perhaps use this as an excuse to try something 'real' and not just a learning exercise. I found the notify crate (https://github.com/notify-rs/notify) and basically copied their example listed on their GitHub, but even this takes about 16-18 hours to place all the watches before it starts processing events. I did not see any obvious ways to enable asynchronous or async/await code in notify, so I don't know of a way to parallelize the disk I/O with this approach.

The notify crate is probably what you're looking for. It uses inotify on linux by default.

There are some proposals on how to do it already such as https://github.com/tokio-rs/axum/issues/1698.

Moreover, I especially like where Rust is right now in the web space. It really feels like there’s a lot of smart people working on the next generation of web development tools - it feels like the place to be. There are a range of great open-source web dev tools that are just reaching critical levels of maturity. Axum, which I used to build Prodzilla, feels ready for out of the box web dev, and is crazy-performant, as I write about later. More recently available is Loco, a Rails-like framework for building web applications in Rust that's picking up steam. And in dev-tooling and hosting there’s Shuttle, a 1-line hosting solution for Rust backends.

CryptoFlow is a full-stack web application built with Axum and SvelteKit. It's a Q&A system tailored towards the world of cryptocurrency!

You also get to specify the accepted HTTP method of the URL via axum::routing. To answer its name, modularity, Axum also supports nested routes as we'll see later in this series. Next is the layer, a method used to apply tower::Layer to all routes before it. This means that routes added after the layer method will not have such a layer applied to their requests. In our case, we used the layer to add tracing to all HTTP requests and responses to our routes. This is needed for proper logging. The tower_http::trace::TraceLayer can even be really customised.

I build simple rust axum api server with Prisma client rust. This is my something done with rust and I really enjoyed rust!

In this article we'll take a comprehensive look at how to use Axum to write a web service. This will also include the 0.7 changes.

You have a couple of options for the underlying web framework to pair with Leptos: Axum or Actix. Axum seems to carry more favour currently, so we start with that. Assuming you already have Rust set up on your system:

I’m the author of https://kellnr.io. When I started working on Kellnr three years ago, https://rocket.rs was “the web framework” to use. Unfortunately, the project seems dead. Before adding more functionality using an unmaintained framework, I want to port Kellnr to https://github.com/tokio-rs/axum.

Web Framework : axum.