Show HN: Feature Flags Backed by Git
11–20 of 46 posts
Re: Show HN: Feature Flags Backed by Git
#12This post comes at a great time! I've been wondering what folks prefer - git or DB backed configs and feature flags. How do you decide to go with one or the other? What do you guys do when GitHub inevitably has an outage?
With DB feature flags, there's one more source of truth for changes to production infra.
(downside, of course, is that changing feature flag values is much slower using git vs DB)
Re: Show HN: Feature Flags Backed by Git
#13Can this probably be done with GitHub Actions and GitHub Pages without any 3rd party platform (just no UI)?
Re: Show HN: Feature Flags Backed by Git
#14This post comes at a great time! I've been wondering what folks prefer - git or DB backed configs and feature flags. How do you decide to go with one or the other? What do you guys do when GitHub inevitably has an outage?
Nice thing about git feature flags: the state of your system is all in one place. It changes only when you do a code release, which includes feature flag values, or an infrastructure release. You can easily see, just off git history, when the state of the system changed (and what changed), which makes incident debugging much easier. With DB feature flags, there's one more source of truth for changes to production inf…
Another benefit is you can easily replicate the current (or previous) state of production/staging/etc flags locally just by doing a `git clone` and then run our self-hosted version locally. Its a single binary, can be installed with curl or homebrew and can read the flag state from your local filesytem.
This allows you to test your code locally or in CI with the same state in production
Re: Show HN: Feature Flags Backed by Git
#15This post comes at a great time! I've been wondering what folks prefer - git or DB backed configs and feature flags. How do you decide to go with one or the other? What do you guys do when GitHub inevitably has an outage?
Re: GitHub outage, each org gets their own instance in our cluster and maintains a checkout of the git state, so you can still write/read from your environments, they just wont be synched to GitHub until they recover.
We're also thinking about adding other 'sinks' like S3/object stores and OCI as backup sinks.
Re: Show HN: Feature Flags Backed by Git
#16If a user can turn a toggle on and off using a UI, what is even the point of Git?
Re: Show HN: Feature Flags Backed by Git
#17If a user can turn a toggle on and off using a UI, what is even the point of Git?
Auditability and, presumably, the ability to require approvals to commit changes are nice to have. I would assume the editor is just a UI to generate a commit. Maybe even to approve them.
Re: Show HN: Feature Flags Backed by Git
#18Re: Show HN: Feature Flags Backed by Git
#19Earlier quoted context omitted.
yeah sorry, I will fix that! It was bothering me too. I put the music to the lowest setting.. I used https://kite.video/
The voice volume seems to get quieter in certain spots, even when its set at a constant level.. I'll reach out to the Kite team
Also happy to manually fix this for you in the meantime if you send us the project file (instructions in the in-app chat).