miniserve VS jelly-actix-web-starter

dufs miniserve

GitHub - svenstaro/miniserve: 🌟 For when you really just want to serve some files over HTTP right now!

And yet C and C++ also have similar functionality. Even if the difference were measured in hundreds of milliseconds, I'd still want to trim down the set of supported formats in my projects and, guess what... the project I most have in mind is an image gallery version of miniserve where I want to statically link everything.

Second this. Both Dufs or Miniserve are good lightweight options.

https://github.com/mufeedvh/binserve https://github.com/svenstaro/miniserve

On a server machine I have Miniserve (a simple service to serve files from a folder over a website) running at 192.168.0.24:50090 or server.local.obfuscated.duckdns.org:50090.

miniserve is an example of an app sort of like that (no SQL, but it'll do file downloads and uploads). I'm currently using it to work on something similar but for quickly throwing up image galleries.

actix-web was the big name in "runs on stable Rust" for a long time and it's what I use, as well as what's used by things like miniserve, paired with Maud.

You can look at https://github.com/secretkeysio/jelly-actix-web-starter

My usual reminder that I have a Django-ish template for actix-web that I maintain: https://github.com/secretkeysio/jelly-actix-web-starter

Now that actix-web 4.0 is out I should be able to finally resolve one of the open issues/PRs, which I was waiting on 4.0 for.

For those interested in Django-in-Rust type approaches, I maintain an actix-web starter project that does exactly this: https://github.com/secretkeysio/jelly-actix-web-starter

I maintain a starter for all of this kind of stuff on top of actix-web, for anyone interested: https://github.com/secretkeysio/jelly-actix-web-starter/

Curious why you went with the mailbox approach - since a request is pretty much in-and-out, I found it sufficient to just write a trait for HttpRequest and have a custom render(...) method that pulls any flash messages from the session, thus clearing them. Wouldn't surprise me if I'm missing something tho.

I love Askama, but being tied to compile time changes is an absurd handicap on a web framework in the initial iteration phase. With Tera, you can implement a watcher for template changes and reload them without needing to recompile the entire framework.

If you want, I have an open source actix-web repo that does stuff like this for you already.

If you enjoy Python's web story but want something similar-ish in Rust, you can check out my actix boilerplate repo - it "mimics" Django in many ways. If nothing else, might be useful for picking apart.