Mender-Client4 Integration with Custom Server Boîte de réception

I’m currently working on a project where I need to integrate the Mender-Client4 with a Django-based centralized update server.

My goal is to manage and deploy updates for NVIDIA-based devices running Linux and microcontrollers. I plan to distribute updates in .deb packages for the Linux systems and .hex firmware files for the microcontrollers.I’m building a Django-based server to handle authentication, update distribution, and tracking. The server will need to authenticate devices and deliver updates in my custom formats.
So i have confused that:
Can my Django server authenticate and distribute updates using Mender’s protocol?if not, what settings do I need to modify in the Mender-Client4 to communicate with my custom Django server? And Since Mender primarily uses .mender artifacts and I am using .deb packages and .hex firmware, do I need to create a custom Mender Update Module to handle these formats properly?

Hi @Hamzaamri,

Thanks for reaching out. I’m not sure I actually understand the question correctly, but condensing it: “Can I write an alternative Mender Server implementation using Python+Django?”

If that is the correct interpretation, then the answer is: “Yes, you just need to implement the API as documented at Mender API docs

But taking a step back, I think you absolutely don’t need to do so. The Mender Artifacts are literally just containers, and you can ship whatever payload with it. It really doesn’t matter if it’s .deb, .hex, whatever. The only thing you need to customize is the Update Module, and for .deb there already is an example implementation: mender-update-modules/deb at master · mendersoftware/mender-update-modules · GitHub

Greetz,
Josef

1 Like