gdb-multiarch-windows VS examples

I tried installing a gdb-multiarch executable from here -- not certain I did it right. Running it it does open the gdb interface, but it doesn't seem to "see" the micro:bit (target/thumbv7em-none-eabihf/debug/led-roulette: No such file or directory.)

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.