Question 1

How do I set up Flippant with PostgreSQL in Elixir?

Accepted Answer

Add the `postgrex` dependency to your mix.exs, then configure the adapter in config.exs with PostgreSQL connection options, similar to the Redis example in the README, ensuring your database is running and accessible.

Question 2

Can Flippant do percentage-based feature rollouts?

Accepted Answer

Not out of the box; Flippant uses group-based rules, so you'd need to create a custom group function that checks user IDs or attributes against a percentage threshold, then enable the feature for that group dynamically.

Question 3

Flippant vs FunWithFlags: which should I use for Elixir?

Accepted Answer

Flippant offers a simpler, actor-focused API with multiple storage adapters, ideal for straightforward group-based toggles. FunWithFlags might be better if you need caching, a web UI, or more built-in features like percentage splits; evaluate based on your project's complexity.

Question 4

How to handle A/B testing with Flippant?

Accepted Answer

Define separate groups for each test variant (e.g., 'group_a' and 'group_b') with custom evaluation functions, enable features for those groups, and track results externally since Flippant doesn't provide analytics.

Question 5

What's the performance impact of using Flippant in production?

Accepted Answer

Minimal if configured correctly; checks involve evaluating groups against actors, but persistent storage like Redis adds network latency, so ensure your adapter is optimized and connections are pooled for efficiency.

Question 6

How to test feature flags locally in development?

Accepted Answer

Use the same adapter configuration as production or a local Redis/PostgreSQL instance; Flippant's runtime management allows enabling features for specific users or mock data during development to simulate different scenarios.

flippant

What is flippant?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions