Skip to content

Conversation

@mwtrew
Copy link
Contributor

@mwtrew mwtrew commented Jan 26, 2026

Status

Points for consideration:

Security

  • Adds a new admin panel at /admin/flipper. This uses a route constraint to deny access to non-admin users (based on session cookie).
  • Disabled feature flags are not shared with the client. However, at present all enabled features are shared with the client, regardless of whether they're expected to have any effect on the client.

Performance

  • In this implementation, each School is a potential Actor (in Flipper terms). Flipper prefers to load feature data once per request and perform membership checks in memory to reduce the number of calls to the DB, but this can be less efficient if there are many Actors. Therefore, by default, there is a limit of 100 Actors per feature. See the Flipper docs - Actors.
  • See also Flipper docs - Performance

What's changed?

  • Adds Flipper UI, allowing admin users to manage feature flags, and an endpoint that exposes enabled feature flags to the client.

Steps to perform after deploying to production

  • Migration(?)

Also adds an endpoint that returns feature flag statuses, following
the example at https://blog.flippercloud.io/client-side-feature-flags/.
@cla-bot cla-bot bot added the cla-signed label Jan 26, 2026
@mwtrew mwtrew marked this pull request as ready for review February 2, 2026 11:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants