Today we released Drogue Cloud 0.5.0. It brings together a lot of things that have been cooking for a while.

Writing code is easy, writing documentation is hard. True, some people might disagree with that. We wanted to make it easier for everyone to understand what we already have, and how it works. As we have multiple major topics (embedded and cloud), we need a modular way of structuring our documentation. Here is our approach.

For the past few weeks, we explored removing the allocator from drogue-device and adapt drivers to a more restrictive Actor model. Read on to learn why and how drogue device will change, and the benefits of this change.

A guided tour of drg, the command line client that aims to make your life easier when interracting with a drogue-cloud instance.

Today we released Drogue Cloud 0.4.0. This is a huge step forward in so many areas, let's take a look.

So far, we didn't really release anything. We created tagged versions, so that you don't need to rely on latest, which might change any second. We had a release pipeline in the CI. Still, it just didn't feel ready enough. This time it is different.

In previous posts we've seen how to run drogue-cloud, how to use LoRaWAN in rust, and the introduction of the drogue-device. In this post, we'll tie this together and walk through the process of running LoRa on drogue-device, sending data to drogue-cloud.

You might have noticed, we talk about Rust a lot. Mostly in the context of embedded programming. However, we also have a few bits and pieces in the cloud side of things. If you have a device that gathers data, you might want to send that data somewhere for further processing and storage. Now, if we are using Rust to implement the embedded side, why not use it on the backend as well?

Trying to bring reusable and efficient components to embedded Rust has been a challenge for our team. We think we've started to make headway, and want to introduce the Drogue Device project.

Good news, everyone! Google Summer of Code 2021 is coming up. This gives you the chance to throw yourself at some horrifying tech problems, learn some new skills, and maybe get to know a few more memes. We are participating, how about you?