1
0
mirror of https://github.com/Unleash/unleash.git synced 2024-12-22 19:07:54 +01:00
unleash.unleash/website/docs/reference/sdks/php.md
Thomas Heartman d5fbd0b743
refactor: move docs into new structure / fix links for SEO (#2416)
## What

This (admittedly massive) PR updates the "physical" documentation
structure and fixes url inconsistencies and SEO problems reported by
marketing. The main points are:

- remove or move directories : advanced, user_guide, deploy, api
- move the files contained within to the appropriate one of topics,
how-to, tutorials, or reference
- update internal doc links and product links to the content
- create client-side redirects for all the urls that have changed.

A number of the files have been renamed in small ways to better match
their url and to make them easier to find. Additionally, the top-level
api directory has been moved to /reference/api/legacy/unleash (see the
discussion points section for more on this).

## Why

When moving our doc structure to diataxis a while back, we left the
"physical' files lying where they were, because it didn't matter much to
the new structure. However, that did introduce some inconsistencies with
where you place docs and how we organize them.

There's also the discrepancies in whether urls us underscores or hyphens
(which isn't necessarily the same as their file name), which has been
annoying me for a while, but now has also been raised by marketing as an
issue in terms of SEO.

## Discussion points

The old, hand-written API docs have been moved from /api to
/reference/api/legacy/unleash. There _is_ a /reference/api/unleash
directory, but this is being populated by the OpenAPI plugin, and mixing
those could only cause trouble. However, I'm unsure about putting
/legacy/ in the title, because the API isn't legacy, the docs are. Maybe
we could use another path? Like /old-docs/ or something? I'd appreciate
some input on this.
2022-11-22 09:05:30 +00:00

3.8 KiB

title
PHP SDK

In this guide we explain how to use feature toggles in a PHP application using Unleash-hosted. We will be using the open source Unleash PHP Client SDK.

You will need your API URL and your API token in order to connect the Client SDK to you Unleash instance. You can find this information in the “Admin” section Unleash management UI. Read more

Step 1: Install the client SDK

First we must add Unleash Client SDK as a dependency to your project. Below is an example of how to install it via composer:

composer require unleash/client guzzlehttp/guzzle symfony/cache

Note: You can install any other PSR-16, PSR-17 and PSR-18 implementations instead of guzzlehttp/guzzle and symfony/cache

Step 2: Create a new Unleash Instance

Next we must initialize a new instance of the Unleash Client.

<?php

use Unleash\Client\UnleashBuilder;

$unleash = UnleashBuilder::create()
    ->withAppName('my.php-app')
    ->withInstanceId('your-instance-1')
    ->withAppUrl('API URL')
    ->withHeader('Authorization', 'API token')
    ->build();

In your app you typically just want one instance of Unleash, and inject that where you need it. You will typically use a dependency injection frameworks to manage this.

You should change the URL and the Authorization header (API token) with the correct values for your instance, which you may locate under “Instance admin” in the menu.

Step 3: Use the feature toggle

Now that we have initialized the client SDK we can start using feature toggles defined in Unleash in our application. To achieve this we have the “isEnabled” method available, which will allow us to check the value of a feature toggle. This method will return true or false based on whether the feature should be enabled or disabled for the current request.

<?php

if ($unleash->isEnabled("AwesomeFeature")) {
  //do some magic
} else {
  //do old boring stuff
}

Read more about the Unleash architecture to learn how it works in more details

Step 4: Provide Unleash Context

It is the client SDK that computes whether a feature toggle should be considered enabled or disabled for specific use request. This is the job of the activation strategies, which are implemented in the client SDK.

The activation strategies is an implementation of rules based on data, which you provide as part of the Unleash Context.

a) As argument to the isEnabled call

The simplest way to provide the Unleash Context is as part of the “isEnabled” call:

<?php

use Unleash\Client\Configuration\UnleashContext;

$context = new UnleashContext(
    currentUserId: 'user@mail.com',
);

$unleash->isEnabled("someToggle", $context);

b) Via a UnleashContextProvider

This is a bit more advanced approach, where you configure a unleash-context provider. By doing this you do not have to rebuild or to pass the unleash-context object to every place you are calling $unleash->isEnabled().

<?php

use Unleash\Client\UnleashBuilder;

$contextProvider = new MyAwesomeContextProvider();
$unleash = UnleashBuilder::create()
    ->withAppName('my.php-app')
    ->withInstanceId('your-instance-1')
    ->withAppUrl('https://unleash.example.com/api/')
    ->withContextProvider($contextProvider)
    ->build();

// Anywhere in the code unleash will get the unleash context from your registered provider.
$unleash->isEnabled("someToggle");

You can read more complete documentation in the Client SDK repository.