Qovery's company blog covers its cloud deployment platform, Kubernetes tooling, and technical posts on Rust, including async streams and memory errors.
HN links it for Rust guides and cloud deployment. Commenters mention Qovery as a French alternative host, and staff post job openings.
Hey everyone, we were doing some repo admin and briefly changed the visibility of the repo from public -> private and back to public, then discovered in horror that we lost ALL the github stars and forks! Googling suggests that others have ran into this issue too and github is not able to restore it (see https://www.qovery.com/blog/we-lost-3800-stars-on-github-in-1-click).
Could you help us by starring our repo and perhaps spread the word? Would really mean a lot! https://github.com/useVenice/venice
PSA: Never change a public repo to private, not even for a moment, because doing so means you will irreversibly lose ALL your github stars and forks, there is no going back! :(
Well written article. This exactly with this spirit - of making AWS, GCP, Azure accessible to any developer that Qovery has been built. The idea of Qovery is to build the future of the Cloud - making developers to deploy their apps on AWS in just a few seconds. No joke. 2200+ developers from 110+ countries are deploying hundreds of apps per day. And this is only the beginning. Thanks again for sharing this article.
You can give a try to Qovery here: https://www.qovery.com
Qovery (https://www.qovery.com) | Container as a Service platform for developers | REMOTE EU / US
* Sr. Backend Engineer -> https://angel.co/company/qovery/jobs/673623-backend-software-engineer-rust-kotlin-go
* Dev Advocate -> https://angel.co/company/qovery/jobs/734995-evangelist-developer-advocate
Join us on https://discord.qovery.com
https://releasehub.com/ (Disclaimer, first listed because I work here)
https://www.quali.com/
https://www.withcoherence.com/
https://webapp.io/
https://www.uffizzi.com/
https://www.qovery.com/
https://www.devzero.io/
These exist in the B2B space (and isn't an exhaustive list), there are a ton more in the B2C space
The article share some common pitfalls people stumble upon when starting using Async in Rust.
If you know some others that are not listed, let's share it in comment :)
P.s: Other tuto article around Stream, if you are starting with Async https://www.qovery.com/blog/a-guided-tour-of-streams-in-rust
The article share some common pitfalls people stumble upon when starting using Async in Rust.
If you know some others that are not listed, let's share it in comment :)
P.s: Other tuto article, if you are starting with Async https://www.qovery.com/blog/a-guided-tour-of-streams-in-rust