graphql-api VS iot_devices

I created an open source library that turns structured text data (YAML) in a Git repository on the fly into a GraphQL API with CRUD queries / mutations.

All that is needed in the repository is a plain text GraphQL schema file that defines what the data structures look like. The Git repository itself can be located on GitHub, GitLab, or in the local filesystem.

https://github.com/commitspark/graphql-api

I'm working on https://commitspark.com , a headless CMS where all data is stored in a GitHub repository with branching/merging workflow support for content.

Reading/writing content from/to GitHub happens through an Open Source API library I released. For the content data schema, I simply require a plaintext GraphQL type file inside the repository. The schema then automatically determines the API structure as well as the editor-friendly UI that I can generate on the Commitspark website when you log in via GitHub.

Even though Commitspark is already publicly available, it is still 100% a side-project that doesn't earn me any money (yet).

Hi HN,

I built Commitspark, a Git-based headless CMS that runs on top of GitHub.

The primary purpose is to enable non-technical content editors to take advantage of Git workflows based on branches, pull requests and merges, without them having to learn Git.

Behind the scenes, everything content-related is driven by GraphQL and an open source library I released ( https://github.com/commitspark/graphql-api ), and for all the workflow features like PRs, commenting and diffs, I built a CMS-centric view onto GitHub using the GitHub API.

For content editors, this should feel the same as working in any other headless CMS, except now with support for much more powerful workflows. For developers, this means all the strengths of Git and GitHub can now also be applied to content (pipelines, tags, commit hashes for caching, branches for migrations, etc.).

There are many other things I am also excited about here that I'm happy to discuss, so please leave your questions below.

Have you considered that content might come from Git? If so, how would content branches fit into this?

(Disclosure: I'm building a library that turns a Git repository into a branch-enabled GraphQL content management API. See https://github.com/contentlab-sh/contentlab )

Wow, what a great idea for a thread!

I'm trying to pare down my personal projects to just the really exciting ones, so I don't have much, butni think the most appropriate to the thread is https://github.com/EternityForest/iot_devices

It's mean to be a cross-framework library for creating device integrations, so you can, say, write a handler for RTL SDR weather stations, and use it in a simple script up to a mega framework.

I kind of dislike the way HASS and others handle automations where they have special purpose primitives for everything that needs lots of hand written code.

I just have config entries, they must be strings, and data points, they can be strings, numbers, bytes, or objects. You can put metadata on them. There's also a few other utilities like the ability to make subdevices, and the ability to request things from the host.

There are no special subclasses, a light bulb is just a device with a brightness point.

It currently runs my security system with object detection recording, QR decoding if desired, multiple regions, motion detection without decoding every frame, and subsecond latency streaming to the browser, a nice recordings browser that can view a recording while it's being made, etc.

My HA platform project started in 2013. Every few months or so I check back to see if HA has progressed far enough that I can ditch one of the last custom apps in my life.

It's getting there. But it's not quite there yet. Last I checked the logging still saves every change, it's not easy to set up so that it will only save average/min/max over time to save SD wear.

Creating new integrations is easy but still not quite a five minute job like it is with my extension API(https://github.com/EternityForest/iot_devices)

But yet, having custom software in one's life is generally IMHO far more of a liability than an asset.

So what I actually do is just use YoLink and Google assistant for everything I possibly can, and use custom software for video recording and unusual stuff YoLink doesn't do.

I'd love to have a one size fits all "If it need automating, use this" platform, and HA seems like it's got the potential.... but just using the YoLink proprietary platform is the lazy, trouble free, super cheap way.

I'm working on a standard for easy drop-in home IoT drivers: https://github.com/EternityForest/iot_devices

Maybe you could go one level of meta up and instead of working on reusable components, work on reusable definitions for component interfaces.

Reuse is hard because you need a bunch of glue code. But if you had, like a standard for a toolbar, that knew how to find all the ToolbarAble objects, and the shopping cart icon just showed up, etc, things would get easier.

The shopping cart could know to look for all the payment requesting components declared in your Big Project File or whatever, and everything could stay modular ish?

GitHub is already the standard place to share generic projects.

Source code can be found here: https://github.com/EternityForest/iot_devices