31–40 of 46 posts
If a user can turn a toggle on and off using a UI, what is even the point of Git?
I like this design choice!! Wondering, what will be the biggest drawback pop in your head compared to traditional DB config or feature flags solution?
Complexity of initial implementation was certainly one, as we developed it. It’s not the most well trodden path for this kind of problem (well trodden for other kinds of apps). Obviously it lacks things like relations and schema, that we have to build on top of data in flat files. One thing is that running Flipt open source on your infra, means running replicas all sourcing from the same Git repo. They currently poll…
Earlier quoted context omitted.
Complexity of initial implementation was certainly one, as we developed it. It’s not the most well trodden path for this kind of problem (well trodden for other kinds of apps). Obviously it lacks things like relations and schema, that we have to build on top of data in flat files. One thing is that running Flipt open source on your infra, means running replicas all sourcing from the same Git repo. They currently poll…
You can get around most of the consistency problem by "scheduling" the change. So, if I know it is going to take 2 minutes to make the flag available to my entire infra, I can schedule it for 5 minutes from now (could even make this configurable—a "default feature delay") which moves the consistency problem to infrastructure clock-sync.
This 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?
Use s3. Honestly.
This 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?
I worked with a mesos config app, backed by git. Watching the whole go down when github died resolved none of us to ever trust it again for that sort of role. Use s3. Honestly.
Flipt Open-Source can be run to consume from these locations. You can go as far as configuring a workflow to publish on push, so that you can combine our managed UI with any of these distributions methods through Git.
With any of these backends (including Git), we periodically fetch and cache data in-memory. Evaluations work on an in-mem snapshot. So temporary downtime doesn't propagate into your applications being unable to get flag evaluations.
Use the same SDK and ping github rest api to get the values of the the flag.
I know, this is very weird... But i cant deny it would be helpful for very small projects
Earlier quoted context omitted.
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
Kite founder here–Sorry about that, we’ll take a look. We have some auto normalization turned on that we obviously need to tweak. Thanks for flagging! Also happy to manually fix this for you in the meantime if you send us the project file (instructions in the in-app chat).
Will send over the project file now, very much appreciated!
Earlier quoted context omitted.
I worked with a mesos config app, backed by git. Watching the whole go down when github died resolved none of us to ever trust it again for that sort of role. Use s3. Honestly.
On this, we support publishing the state to object storage (S3, Azure, GCS) and to OCI as well in Flipt. Flipt Open-Source can be run to consume from these locations. You can go as far as configuring a workflow to publish on push, so that you can combine our managed UI with any of these distributions methods through Git. With any of these backends (including Git), we periodically fetch and cache data in-memory. Evalu…
This 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?
Earlier quoted context omitted.
This is my question. If your flags are in your repo, what is functionally the difference from just having them be variables in your code somewhere. "Feature Flags that live inside your code" - That's just variables, no?
Feature flag state is still served dynamically through Flipt. Your code doesn’t have to redeploy for the changes to “become live”. That’s the main benefit. Means you can experiment and target different cohorts with variants of your app without restarting processes everywhere.