1
0
mirror of https://github.com/Unleash/unleash.git synced 2025-09-10 17:53:36 +02:00

fix: update docs

This commit is contained in:
Fredrik Oseberg 2021-08-13 12:18:10 +02:00
parent 716090a659
commit a56e1caa04
2 changed files with 4 additions and 2 deletions

View File

@ -13,6 +13,8 @@ Activation strategies compound, and every single strategy will be evaluated. If
> Unless you add activation strategies on toggle creation, the toggle will be created with the default strategy. The default strategy says that the toggle is either 100% off or 100% on for all users. This means that any other strategies you add will have no effect. If you want to use strategies to control rollout you need to remove the default strategy. > Unless you add activation strategies on toggle creation, the toggle will be created with the default strategy. The default strategy says that the toggle is either 100% off or 100% on for all users. This means that any other strategies you add will have no effect. If you want to use strategies to control rollout you need to remove the default strategy.
Unleash comes with a set of built in strategies. [But you can also build your own custom strategies.](../advanced/custom_activation_strategy)
[You can read more about activation strategies here.](./activation_strategy) [You can read more about activation strategies here.](./activation_strategy)
## Local evaluation ## Local evaluation

View File

@ -9,7 +9,7 @@ Welcome to the Unleash documentation. Our goal with our documentation is to guid
One of the most important aspects of the architecture to understand is that feature toggles _are evaluated in a client SDKs_ which runs as part of your application. This makes toggle evaluations super-fast (_we talk nano-seconds_), scalable and resilient against network disturbances. In order to achieve this Unleash compromises a small update-delay when you change your toggle configurations until it is fully propagated to your application (in terms of seconds and is configurable). One of the most important aspects of the architecture to understand is that feature toggles _are evaluated in a client SDKs_ which runs as part of your application. This makes toggle evaluations super-fast (_we talk nano-seconds_), scalable and resilient against network disturbances. In order to achieve this Unleash compromises a small update-delay when you change your toggle configurations until it is fully propagated to your application (in terms of seconds and is configurable).
If you want more details you cam read about [our unique architecture](https://www.getunleash.io/blog/our-unique-architecture). If you want more details you can read about [our unique architecture](https://www.getunleash.io/blog/our-unique-architecture).
### Unleash Server {#unleash-server} ### Unleash Server {#unleash-server}
@ -21,7 +21,7 @@ Before you can connect your application to Unleash you need a Unleash server. Yo
- [Click-to-deploy on Heroku](https://www.heroku.com/deploy/?template=https://github.com/Unleash/unleash) - [Click-to-deploy on Heroku](https://www.heroku.com/deploy/?template=https://github.com/Unleash/unleash)
2. **Unleash Enterprise** 2. **Unleash Enterprise**
- [Hosted Plans](https://www.getunleash.io/plans) - [Hosted Plans](https://www.getunleash.io/plans)
- [Self-hosted](https://www.unleash-hosted.com/articles/self-host-your-feature-toggle-system/) - [Self-hosted](https://www.getunleash.io/blog/self-host-your-feature-toggle-system)
### System Overview {#system-overview} ### System Overview {#system-overview}