actix-web | Actix Web | HTTP library

Look at the examples in the docs for Data. It seems you have to put your initialized struct in a Mutex and then add that to your App. Also beware that you need to include it in your path fn as a Mutex as well.

Looking at the documentation of actix_files::Files:

The first argument (mount_path) is the root URL at which the static files are served.

The second argument (serve_from) is the location on disk at which files are loaded.

You are using /static as first argument, so your files will be under http://0.0.0.0:80/static, all right.

But as second argument you set . that is the root of the project. This means that you are publishing the whole source of your project! For example, at http://0.0.0.0:80/static/src/main.rs (http://0.0.0.0:80/static/ is the mount point, ./src/main.rs is the local file) you will download the source of your binary, and you do not want that.

To fix your problem write instead:

In your case token is a local variable and a reference to it (&token) is definitely not with a static lifetime. The compiler error explains it and shows it to you.

You probably want to create a HeaderValue instance some other way, not via from_static. For example like this: HeaderValue::from_str(&token).

Solved it by wrapping the UdpSocket in an Arc and keeping the reference in the actor for later use. Using the socket to write messages works. The split stream used for the streamhandler needs no change, as it works as expected.

An async function returns a Future, you need to await the future to get the result. In your case the Responder:

I think there are 2 problems here:

• Looks like you forgot to add EXPOSE 8000 to your dockerfile.
• Since you forgot to add expose I supposed you also forgot to bind your port when running your image: docker run -p 8000:8000 image_name

You need to specify the Data type to app_data with turbo fish syntax.

Try NOT (interface_id = ANY($2)) where $2 is ToSql of a Vec / slice of whatever type interface_id is.

Often these simple array queries can have the same execution plan as their IN / NOT IN equivalents - but double check an EXPLAIN to be sure.

This is mentioned in the actix_web Changes.md for v4.0:

The client mod was removed. Clients should now use awc directly.

The actix_web::client module has long since largely been a wrapper around the awc crate ever since the 1.0 release, but it seems they now want to separate them entirely.

The types from awc should be near identical to those exposed in prior actix_web releases, however if you're using it with actix_web:4.0 (currently in beta) then you'll want to use awc:3.0 (currently in beta) for compatibility.