teloxide VS rust-embed

I'm using teloxide, which is a crate for building Telegram bots. I have a small Telegram bot running on my Raspberry Pi, and since it's very slow to compile, I'm trying to cross compile it from my Windows machine, with no luck.

I do completely agree with your advice of using `Arc`s. But unfortunately, sometimes it gets very tedious to deal with all these `Arc`s: https://github.com/teloxide/teloxide/blob/ec1d41220c51872cf9....

It also blurs the advantage of Rust as a lifetime validation tool if you use reference counting anyways. But it seems that it's the only viable approach for async at the moment.

A Telegram bot built with Rust Telegram bot framework Teloxide, used to provide support to new users discovering our network, and to help them navigate through our channels of information by using various commands to interact with and find a job as fast as possible without need for visiting /jobs page from our website.

There is https://github.com/teloxide/teloxide though, maybe there is a confusion? It's actively maintained?

This is prototype and we plan to include more features. The bot is built with Rust Teloxide framework and we plan to deploy more Rust code for our production code, web pages and end points.

We also built a Telegram bot with Rust Teloxide framework and will deploy this week and show that is is written in Rust also.

Working on teloxide, a Telegram bots framework for Rust.

As was said earlier, for visibility purposes, gRPC client is also a Telegram bot. To implement the bot, teloxide library was used.

You can also make some social media bots with Rust

Ref: https://github.com/pyrossh/rust-embed/issues/205 Rust-embed behavior in debug mode is incompatible with cross-compilation. It nails a path from build time into the executable. Force release mode o"

Not sure how common it is exactly but I've definitely seen it done here and there and done it myself in some projects. Having self-contained binaries is super nice and avoids a fair few issues. rust-embed makes it even better.

They even accepted one of my feature requests to add some file metadata which makes doing this kind of thing easier: https://github.com/pyros2097/rust-embed/issues/140

Note: include_str! can make compilation a bit slow. The rust-embed crate can read files in debug mode as normal and embed the files in release mode.

For reference, there are examples for several frameworks in the rust-embed repo.

But then it turned out that the images can’t be read from the database due to the lack of GridFS support in MongoDB Rust Driver (open ticket). So for simplicity purposes, I decided to use rust_embed crate which allows including images in the application binary at compile time (at the development time they are loaded from a file system). (It is also possible to store images separately from the application; images folder should be mounted as a volume in the Docker Compose service definition)

Images of planets are included in the application binary at compile time using rust_embed crate (at the development time they are loaded from a file system).

Maybe rust-embed can help you? I haven't used it myself, just came across the crate on this sub a while ago.