I'm currently working on a Python service that monitors various IoT devices including industrial motors and cold storage units. Each device has its own folder containing specific configuration files: a `.config` file for runtime parameters, a `schema.json` describing the sensor input, and a `description.txt` explaining the device's purpose and monitoring methods. I'm seeking a solution that provides a web interface to easily create, edit, and delete these device folders. Additionally, I need a backend—either self-hosted or cloud-based—where my Python service can query to fetch this configuration data at runtime.
4 Answers
Consider looking into OpenRemote or ThingsBoard. They may require some extra coding to integrate, but they could provide a good starting point for managing your device configurations. If a GUI isn’t a priority, you might want to explore using Puppet instead for an easier setup!
Ansible or Nix could also be good options to consider for managing your configuration needs.
Decoupling the device folders from your main repo seems like a smart move. For a quick solution, you could use a separate Git repo for your device folders. If you're not keen on Git, spinning up a MinIO instance or using S3 with Filestash for file management through the browser could be really effective. This way, your Python service can fetch configurations from the object storage seamlessly.
Have you checked out Prometheus? It's really good for metrics monitoring, although it might not be exactly what you need for configuration management. It offers some great service discovery systems, but it seems like you want something more tailored to your specific requirements.
Thanks for the suggestion! Prometheus is indeed a solid tool for monitoring. However, I'm looking for a more flexible and structured configuration management system that can handle the specific logic of my application. But I really appreciate the tip!
Great idea! I hadn’t thought of using Filestash with object storage for managing configurations. It feels like a perfect balance between a full-blown CMS and developing something from scratch. I might just go for this setup!