One of my favorite things about this is that we are bringing a GitOps workflow to IT teams. As a software engineer myself, seeing change management and CI coming to other domains within the organization is incredibly exciting!
Source code for Fleet is available at https://github.com/fleetdm/fleet.
I made a bot last summer to generate and update weekly Spotify playlists from 100 or so music subreddits based on the top submissions of that week. Update operates entirely through a GitHub action so no resource spending.
I don’t often finish my side projects so was pretty happy to have something finally usable and shareable, it’s been fun showing friends!
Fleet is building an open future for device management. Open APIs you can use from anywhere. Transparency for end-users. Trust built on an open-core foundation.
We are looking for an Engineering Manager on our Agent team. This position will be responsible for managing the engineers and strategy for:
- Osquery across Windows, macOS, and Linux. - Fleet's agent update system based on The Update Framework. - Fleet Desktop (Desktop application for user notifications and self-remediation). - MDM features.
Join our team of friendly and competent engineers to expand our 100% source-available (github.com/fleetdm/fleet) endpoint management product. We work closely with the osquery community, and have both paying customers and open-source users from organizations you’ve heard of. We’re backed by CRV and Sid Sijbrandij (CEO of GitLab).
This role will report directly to me (CTO), please reach out with any questions: zach[at]fleetdm.com
I’m guessing virtual table extensions work with this since you’re just replacing the storage engine? So we could in theory use FTS5 and even OSQuery and other extensions right?
However since this is using FoundationDB I’m also guessing we can’t use this as a serverless embedded DB since since you’ll probably need a foundation db cluster to use this. Is that right?
So if I understand correctly this is a SQLite query engine on top of FoundationDB with distributed transactions and we can theoretically use SQLite ecosystem stuff like FTS5 and datasette on top of it.
In theory osquery is "just" virtual tables, but in practice there's quite a bit more that would probably make attaching it to mvsqlite. If you have a use case in mind I would love to know!