actix-tls directly depends on two different versions of http?! https://github.com/actix/actix-net/blob/main/actix-tls/Cargo.toml

#rust #rustlang #actix

actix-net/actix-tls/Cargo.toml at main · actix/actix-net

A collection of lower-level libraries for composable network services. - actix/actix-net

GitHub
In #rust / #rustlang I have a #HTTP endpoint (#actix) , where for a given query, it fetches #JWT from the given parameter (URLS) and validates, puts some logic and returns the result. How to write unittest for this care in rust?
Now installing #actix comes with 175 dependencies…

Really not a fan of that either, especially given the generally alpha-state of the ecosystem, but let’s see…


#DependencyHell

https://rocket.rs/guide/v0.5/faq/#in-prod

While Rocket is still in the 0.x phase, the version number is purely a stylistic choice. In fact, we consider Rocket to be the most mature web framework in the Rust ecosystem. To our knowledge, Rocket is the only Rust web framework that correctly implements: […]Dear #Rocket devs: Please read the fucking semver spec!If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backward compatibility, you should probably already be 1.0.0. If you are so immature as to not even follow what to me feels like just about the easiest standard in software-development to follow, how can I trust that you follow the less obvious standards that actually matter?

It’s like a pharmacist claiming that he cleaned his entire body before mixing your injections and that nobody does it more thoroughly than him, but his pants are covered in dirt: The pants technically don’t matter, what matters is that his hands were clean, but it really calls into question his other claims…

If you're coming from a different ecosystem, you should feel comfortable considering Rocket's v0.x as someone else's vx.0. Rust points to the semver standard and that standard disagrees with you.Rust and Cargo's semver policy, and Rocket's strict adherence to it, ensures that Rocket will never break your application when upgrading from 0.x.y to 0.x.z, where z >= y. Furthermore, we backport all security and correctness patches to the previous major release (0.{x-1}.y), so your application remains secure if you need time to upgrade.What major releases? You don’t have any!

And if you treat your minor releases as major releases, that means that you have no distinction between minor releases and patches left…

Well, it’s not that rocket is alone in that regard, but it at least makes the choice easier, sine it really cuts down on frameworks that seem to primarily be successful due to SEO, rather than maturity. I’m now looking at
#actix as a starting point, since they at least pass the sniff-test of getting versioning right and seem to support what I might need…

#zerover #semver #rust #rustlang

FAQ - Rocket Web Framework

Rocket is a web framework for the Rust programming language that makes it simple to write fast web applications without sacrificing flexibility or type safety.

🦀 actix-passport: A comprehensive, flexible authentication framework for actix-web applications in Rust.

https://github.com/densumesh/actix-passport

#actix #rust #webdev #auth

GitHub - densumesh/actix-passport: A comprehensive, flexible authentication framework for actix-web applications in Rust.

A comprehensive, flexible authentication framework for actix-web applications in Rust. - densumesh/actix-passport

GitHub
I'm wondering if writing my own "web server" to serve my website/blog (the same as my Neocities, but eventually with some twists I couldn't do on Neocities) might be a good idea to force me into a "project" (and help me learn Rust better).

I'm currently reading this blog post and the whole process looks genuinely fun: https://mortenvistisen.com/posts/how-to-build-a-simple-blog-using-rust

(Bonus point: The blog post is also about Tera, which I already use on my Neocities since I'm using Zola as a static site generator, so it will probably help if I port my website's own template to the new custom thing)

#Rust #Actix #Tera
Learning Rust by creating your own blog | MBV

Hands-on tutorial that teaches you web development with Rust by creating your own blog

Learning Rust by creating your own blog | MBV

Telegram AI Companion: веселый проект на Rust, Telegram и локальном ИИ

Привет, Хабр! 👋 Недавно я собрал небольшой, но бодрый pet-проект — Telegram AI Companion . Это Telegram-бот, который умеет болтать с вами, используя локальную языковую модель через LocalAI . Без OpenAI, без облаков — всё на своём железе. Цель проекта — не революция в AI, а именно учебное и увлекательное погружение в Rust , асинхронность, Telegram API и локальные LLM-модели. Такой себе “бот-компаньон”, но больше для разработчика, чем пользователя :) Если вам интересно:

https://habr.com/ru/articles/920482/

#rust #telegram_bot #localai #llm #docker #actix #openai #ai #ngrok #natural_language_processing

Telegram AI Companion: веселый проект на Rust, Telegram и локальном ИИ

Привет, Хабр! 👋 Недавно я собрал небольшой, но бодрый pet-проект — Telegram AI Companion . Это Telegram-бот, который умеет болтать с вами, используя локальную языковую модель через LocalAI . Без...

Хабр

Well, now my #torrent #tracker udp://chihaya.de:6969 running #torrust #actix is using 8 cores, 14gb ram, 830mb DB size. That escalated quickly. Current stats:

[torrust_actix] [STATS] Torrents: 12650498
- Updates: 71081 - Seeds: 251455 - Peers: 782356 - Completed: 591511

Good progress on the #dweb REST APIs and improvements to the #OpenAPI docs today, all with the help of #actix and #utoipa

BTW #SwaggerUI is really cool

A few days ago I knew nothing about these but now I have a working API that is documented and can be tested live while reading those docs.

Someone asked if I might support #GraphQL but I haven't looked into that. Convince me that I should!

Baby steps building my first #REST API into #dweb using #actix and now wondering how to document it.

First impression is #utoipa (more active and possibly suitable than #apisto) so I'll try the former first.

Opinions and experiences with these and other options welcome!
#OpenAPI #Rustlang