examples VS jelly-actix-web-starter

I was taking a look at: https://github.com/actix/examples/blob/master/forms/multipart/src/main.rs

Using aws-sdk-s3 requires that tokio is installed. The above code was drafted from actix forms with multipart and s3 example with few modifications. There is a Client wrapper with two main endpoints: upload and delete_file. upload uses put_object_from_file to upload files to S3 and returns the uploaded files' URLs while delete_file deletes a file. We also created some type in backend/src/types/upload.rs:

I just figured it out. I had this: https://github.com/actix/examples/blob/master/databases/postgres/Cargo.toml as my toml, and somehow I removed the actix-web.workspace = true tag, but I didn't see the derive_more one. Removed it and that fixed it.

It doesn't need to be in another directory, creating separate folder for static content is common practice, it makes your project organization more clear and minimizes errors with overlapping and over-complicated routes/paths. Take a look at folder structure of the example project found from actix-files repository: https://github.com/actix/examples/tree/master/basics/static-files, it's great starting point where you can start extending it for your own needs.

There's an example of using MongoDB with actix-web here: https://github.com/actix/examples/tree/master/databases/mongodb

Sorry for the late response. Here is an example of how I implemented it using axum and rustls, and there is a similar example for actix-web here. It looks like the actix-web example follows much the same process for parsing the key and cert files and creating the rustls server config so hopefully the tls module in my example can provide some help.

As of now, I can register a new user by storing a username and hashed password, and then my login page is able to insert a user's ID into my Session per this example. The problem is that when I navigate from the login page after successfully inserting a new key, the Session doesn't persist to the next page.

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.