Implementing feature flags in Laravel

[tawdry frost]

Hi,

I am the creator of Featurevisor, an open source feature flags management tool: https://featurevisor.com/

it comes with a PHP SDK too here: https://featurevisor.com/docs/sdks/php/

I am curious to understand if there are any well established ways of implementing feature flags in Laravel already, and I am keen to produce guides covering this framework for others to read then.

areas I am looking into:

• intercepting requests for evaluating flag values against individual users (like for gradual rollouts)
• handing over pre-evaluated values to frontend (so frontend can pick things up with JavaScript SDK)
• usage of any cache layer for fetching/storing the configuration

any directions highly appreciated 🙌

Thanks

[obsidian acorn]

Check out https://laravel.com/docs/12.x/pennant

Looks like your package does a lot more, but you should probably explain how exactly it differs from Pennant, since that's the "official" package.

[waxen totem]

Have you ever used feature flags for the backend with Laravel as an API? If so, do you have any examples? This is just a discussion, not a request for help.

[tawdry frost]

Thanks @obsidian acorn, will study the Pennant API.

The way I’m approaching the solution, the configuration comes from outside of the application (could be in either PHP, JavaScript, etc) in a platform agnostic way.

New configs can be fetched and evaluated in the applications without needing to re-deploy them.

Therefore not tied to the application directly.