2021-06-04 19:38:35 +02:00
< div align = "center" >
2021-06-04 19:31:28 +02:00
2023-11-14 14:56:25 +01:00
< a href = "https://getunleash.io" title = "Unleash - Empowering developers to release with confidence" >
< img src = "./.github/github_header_opaque_landscape.svg" alt = "Visit the Unleash website" >
2022-04-07 15:41:49 +02:00
< / a >
2022-04-08 13:39:44 +02:00
< br / >
< br / >
2022-05-06 11:17:35 +02:00
2022-12-19 10:23:07 +01:00
[](https://github.com/Unleash/unleash/actions/workflows/build.yaml) [](https://coveralls.io/github/Unleash/unleash?branch=main) [](https://hub.docker.com/r/unleashorg/unleash-server) [](https://github.com/Unleash/unleash/blob/main/LICENSE) [](https://slack.unleash.run)
2021-06-21 20:08:58 +02:00
2023-11-14 14:56:25 +01:00
[Experience Unleash Live Demo → ](https://www.getunleash.io/interactive-demo )
2022-10-04 14:04:28 +02:00
2021-06-04 19:38:35 +02:00
< / div >
2021-06-04 19:31:28 +02:00
2023-11-14 14:56:25 +01:00
## What is Unleash?
2022-04-06 10:23:33 +02:00
2023-11-14 14:56:25 +01:00
Unleash is a powerful open source solution for feature management. It streamlines your development workflow, accelerates software delivery, and empowers teams to control how and when they roll out new features to end users. With Unleash, you can deploy code to production in smaller, more manageable releases at your own pace.
2022-04-06 10:23:33 +02:00
2023-11-14 14:56:25 +01:00
Feature flags in Unleash let you test your code with real production data, reducing the risk of negatively impacting your users' experience. It also enables your team to work on multiple features simultaneously without the need for separate feature branches.
2022-04-07 15:22:08 +02:00
2023-11-14 14:56:25 +01:00
Unleash is the most popular open source solution for feature flagging on GitHub. It supports 15 official client and server SDKs and over 15 community SDKs. You can even create your own SDK if you wish. Unleash is compatible with any language and framework.
2022-04-06 10:48:44 +02:00
2022-04-08 13:38:28 +02:00
< br / >
2023-11-14 14:56:25 +01:00
## Getting Started with Unleash
2022-04-06 10:23:33 +02:00
2023-11-14 14:56:25 +01:00
### 1. Setting Up Unleash
2022-04-06 10:23:33 +02:00
2023-11-14 14:56:25 +01:00
To get started with Unleash, you need [`git` ](https://git-scm.com/ ) and [`docker` ](https://www.docker.com/ ) installed on your machine.
2022-04-06 10:23:33 +02:00
2023-11-14 14:56:25 +01:00
Execute the following commands:
2022-06-27 10:17:44 +02:00
```bash
2022-12-12 20:40:18 +01:00
git clone git@github.com:Unleash/unleash.git
cd unleash
2022-04-06 10:23:33 +02:00
docker compose up -d
```
2022-04-08 15:17:06 +02:00
Then point your browser to `localhost:4242` and log in using:
2022-06-27 10:17:44 +02:00
- username: `admin`
- password: `unleash4all`
2022-04-06 10:23:33 +02:00
2022-05-18 12:16:04 +02:00
If you'd rather run the source code in this repo directly via Node.js, see the [step-by-step instructions to get up and running in the contributing guide ](./CONTRIBUTING.md#how-to-run-the-project ).
2022-04-06 10:23:33 +02:00
### 2. Connect your SDK
Find your preferred SDK in [our list of official SDKs ](#unleash-sdks ) and import it into your project. Follow the setup guides for your specific SDK.
If you use the docker compose file from the previous step, here's the configuration details you'll need to get going:
2022-06-27 10:17:44 +02:00
2022-04-06 10:23:33 +02:00
- For front-end SDKs, use:
2022-12-12 20:40:18 +01:00
- URL: `http://localhost:4242/api/frontend/`
- `clientKey` : `default:development.unleash-insecure-frontend-api-token`
2022-04-06 10:23:33 +02:00
- For server-side SDKs, use:
2022-06-27 10:17:44 +02:00
- Unleash API URL: `http://localhost:4242/api/`
2022-04-06 10:23:33 +02:00
- API token: `default:development.unleash-insecure-api-token`
If you use a different setup, your configuration details will most likely also be different.
2021-06-04 19:31:28 +02:00
2024-05-27 09:46:26 +02:00
### Check a feature flag
2022-04-07 15:26:04 +02:00
2024-05-27 09:46:26 +02:00
Checking the state of a feature flag in your code is easy! The syntax will vary depending on your language, but all you need is a simple function call to check whether a flag is available. Here's how it might look in Java:
2022-04-07 15:26:04 +02:00
```java
if (unleash.isEnabled("AwesomeFeature")) {
// do new, flashy thing
} else {
// do old, boring stuff
}
```
2022-04-07 15:40:26 +02:00
### Run Unleash on a service?
If you don't want to run Unleash locally, we also provide easy deployment setups for Heroku and Digital Ocean:
[](https://www.heroku.com/deploy/?template=https://github.com/Unleash/unleash) [](https://cloud.digitalocean.com/apps/new?repo=https://github.com/Unleash/unleash/tree/main& refcode=0e1d75187044)
2022-04-08 13:25:36 +02:00
### Configure and run Unleash anywhere
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 10:05:30 +01:00
The above sections show you how to get up and running quickly and easily. When you're ready to start configuring and customizing Unleash for your own environment, check out the documentation for [getting started with self-managed deployments ](https://docs.getunleash.io/reference/deploy/getting-started ), [Unleash configuration options ](https://docs.getunleash.io/reference/deploy/configuring-unleash ), or [running Unleash locally via docker ](https://docs.getunleash.io/tutorials/quickstart#i-want-to-run-unleash-locally ).
2022-04-08 13:25:36 +02:00
2022-04-08 13:38:28 +02:00
< br / >
2022-04-07 16:01:26 +02:00
## Online demo
2022-04-06 10:24:09 +02:00
2022-04-07 16:01:26 +02:00
Try out [the Unleash online demo ](https://www.getunleash.io/interactive-demo ).
2022-06-09 10:44:06 +02:00
[](https://www.getunleash.io/interactive-demo)
2022-04-08 10:59:47 +02:00
2022-04-08 13:38:28 +02:00
< br / >
2022-04-07 16:01:26 +02:00
## Community and help — sharing is caring
We know that learning a new tool can be hard and time-consuming. We have a growing community that loves to help out. Please don't hesitate to reach out for help.
[](https://slack.unleash.run)
2022-04-06 10:24:09 +02:00
2022-04-08 13:32:11 +02:00
💬 [Join Unleash on Slack ](https://slack.unleash.run ) if you want ask open questions about Unleash, feature toggling or discuss these topics in general.
2022-04-08 11:04:43 +02:00
💻 [Create a GitHub issue ](https://github.com/Unleash/unleash/issues/new ) if you have found a bug or have ideas on how to improve Unleash.
📚 [Visit the documentation ](https://docs.getunleash.io/ ) for more in-depth descriptions, how-to guides, and more.
2022-04-06 10:24:09 +02:00
2023-09-25 15:19:33 +02:00
📖 Learn more about the principles of building and scaling [feature flag ](https://docs.getunleash.io/topics/feature-flags/feature-flag-best-practices ) solutions.
2022-04-08 13:38:28 +02:00
< br / >
2022-04-06 10:24:09 +02:00
## Contribute to Unleash
2023-09-25 15:19:33 +02:00
Unleash is the largest [open source feature flag solution ](https://www.getunleash.io/ ) on GitHub. Building Unleash is a collaborative effort, and we owe a lot of gratitude to many smart and talented individuals. Building it together with the community ensures that we build a product that solves real problems for real people. We'd love to have your help too: Please feel free to open issues or provide pull requests.
2022-04-06 10:24:09 +02:00
Check out [the CONTRIBUTING.md file ](./CONTRIBUTING.md ) for contribution guidelines and the [Unleash developer guide ](./website/docs/contributing/developer-guide.md ) for tips on environment setup, running the tests, and running Unleash from source.
2021-06-04 19:31:28 +02:00
2022-04-22 09:08:20 +02:00
### Contributors
2022-04-22 09:10:34 +02:00
< div align = "center" >
2022-04-22 09:08:20 +02:00
[](https://github.com/Unleash/unleash/graphs/contributors)
2022-04-22 09:10:34 +02:00
< / div >
2022-04-08 13:38:28 +02:00
< br / >
2022-04-08 12:21:33 +02:00
## Features our users love
### Flexibility and adaptability
2024-05-27 09:46:26 +02:00
- Get an easy overview of all feature flags across all your environments, applications and services
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 10:05:30 +01:00
- Use included [activation strategies ](https://docs.getunleash.io/reference/activation-strategies ) for most common use cases, or use a [custom activation strategy ](https://docs.getunleash.io/reference/custom-activation-strategies ) to support any need you might have
2024-05-27 09:46:26 +02:00
- Organise feature flags by [feature flag tags ](https://docs.getunleash.io/reference/tags )
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 10:05:30 +01:00
- [Canary releases / gradual rollouts ](https://docs.getunleash.io/reference/activation-strategies#gradual-rollout )
- Targeted releases: release features to specific [users ](https://docs.getunleash.io/reference/activation-strategies#userids ), [IPs ](https://docs.getunleash.io/reference/activation-strategies#ips ), or [hostnames ](https://docs.getunleash.io/reference/activation-strategies#hostnames )
- [Kill switches ](https://docs.getunleash.io/reference/feature-toggle-types#feature-toggle-types )
2022-04-08 12:21:33 +02:00
- [A/B testing ](https://docs.getunleash.io/topics/a-b-testing )
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 10:05:30 +01:00
- 2 [environments ](https://docs.getunleash.io/reference/environments )
2022-04-08 12:21:33 +02:00
- Out-of-the-box integrations with popular tools ([Slack](https://docs.getunleash.io/addons/slack), [Microsoft Teams ](https://docs.getunleash.io/addons/teams ), [Datadog ](https://docs.getunleash.io/addons/datadog )) + integrate with anything with [webhooks ](https://docs.getunleash.io/addons/webhook )
2024-05-27 09:46:26 +02:00
- [Dashboard for managing technical debt ](https://docs.getunleash.io/reference/technical-debt ) and [stale flags ](https://docs.getunleash.io/reference/technical-debt#stale-and-potentially-stale-toggles )
2022-06-27 10:17:44 +02:00
- API-first: _everything_ can be automated. No exceptions.
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 10:05:30 +01:00
- [12 official client SDKs ](https://docs.getunleash.io/reference/sdks#official-sdks ), and ten [community-contributed client SDKs ](https://docs.getunleash.io/reference/sdks#community-sdks )
2022-04-08 12:21:33 +02:00
- Run it via Docker with the [official Docker image ](https://hub.docker.com/r/unleashorg/unleash-server ) or as a pure Node.js application
2022-04-08 15:17:06 +02:00
### Security and performance
2022-04-08 12:21:33 +02:00
- Privacy by design (GDPR and Schrems II). End-user data never leaves your application.
- [Audit logs ](https://docs.getunleash.io/advanced/audit_log )
- Enforce [OWASP's secure headers ](https://owasp.org/www-project-secure-headers/ ) via the strict HTTPS-only mode
2022-06-27 10:17:44 +02:00
- Flexible hosting options: host it on premise or in the cloud (_any_ cloud)
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 10:05:30 +01:00
- Scale [the Unleash Proxy ](https://docs.getunleash.io/reference/unleash-proxy ) independently of the Unleash server to support any number of front-end clients without overloading your Unleash instance
2022-04-08 12:21:33 +02:00
### Looking for more features?
If you're looking for one of the following features, please take a look at our [Pro and Enterprise plans ](https://www.getunleash.io/plans ):
2022-06-27 10:17:44 +02:00
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 10:05:30 +01:00
- [role-based access control (RBAC) ](https://docs.getunleash.io/reference/rbac )
- [single sign-on (SSO) ](https://docs.getunleash.io/reference/sso )
2022-04-08 12:21:33 +02:00
- more environments
2024-05-27 09:46:26 +02:00
- [feature flags project support ](https://docs.getunleash.io/reference/projects )
2022-04-08 12:21:33 +02:00
- [advanced segmentation ](https://docs.getunleash.io/reference/segments )
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 10:05:30 +01:00
- [additional strategy constraints ](https://docs.getunleash.io/reference/strategy-constraints )
2022-04-08 12:21:33 +02:00
- tighter security
- more hosting options (we can even host it for you!)
2021-06-04 19:31:28 +02:00
2022-04-08 15:16:00 +02:00
< br / >
2022-04-08 12:51:08 +02:00
## Architecture
2022-05-06 11:17:35 +02:00
< img src = "./website/static/img/unleash-architecture.svg" title = "Unleash System Overview" / >
2022-04-08 12:51:08 +02:00
2023-11-13 12:42:26 +01:00
Read more in the [_system overview_ section of the Unleash documentation ](https://docs.getunleash.io/understanding-unleash/unleash-overview#system-overview ).
2022-04-08 12:51:08 +02:00
2022-04-08 15:16:00 +02:00
< br / >
2021-06-14 21:35:19 +02:00
## Unleash SDKs
2021-06-04 19:31:28 +02:00
2022-04-08 12:53:47 +02:00
To connect your application to Unleash you'll need to use a client SDK for your programming language.
2021-05-27 23:36:59 +02:00
2022-04-08 13:32:11 +02:00
**Official server-side SDKs:**
2014-11-10 16:25:22 +01:00
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 10:05:30 +01:00
- [Go SDK ](https://docs.getunleash.io/reference/sdks/go )
- [Java SDK ](https://docs.getunleash.io/reference/sdks/java )
- [Node.js SDK ](https://docs.getunleash.io/reference/sdks/node )
- [PHP SDK ](https://docs.getunleash.io/reference/sdks/php )
- [Python SDK ](https://docs.getunleash.io/reference/sdks/python )
- [Ruby SDK ](https://docs.getunleash.io/reference/sdks/ruby )
2022-01-21 10:20:51 +01:00
- [Rust SDK ](https://github.com/unleash/unleash-client-rust )
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 10:05:30 +01:00
- [.NET SDK ](https://docs.getunleash.io/reference/sdks/dotnet )
2014-11-10 16:39:17 +01:00
2022-04-08 12:53:47 +02:00
**Official front-end SDKs:**
2021-06-14 21:35:19 +02:00
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 10:05:30 +01:00
The front-end SDKs connects via the [Unleash Proxy ](https://docs.getunleash.io/reference/unleash-proxy ) in order to ensure privacy, scalability and security.
2020-01-17 14:02:03 +01:00
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 10:05:30 +01:00
- [Android Proxy SDK ](https://docs.getunleash.io/reference/sdks/android-proxy )
2023-01-03 13:07:01 +01:00
- [Flutter Proxy SDK ](https://docs.getunleash.io/reference/sdks/flutter )
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 10:05:30 +01:00
- [iOS Proxy SDK ](https://docs.getunleash.io/reference/sdks/ios-proxy )
- [JavaScript Proxy SDK ](https://docs.getunleash.io/reference/sdks/javascript-browser )
- [React Proxy SDK ](https://docs.getunleash.io/reference/sdks/react )
- [Svelte Proxy SDK ](https://docs.getunleash.io/reference/sdks/svelte )
- [Vue Proxy SDK ](https://docs.getunleash.io/reference/sdks/vue )
2022-01-21 10:20:51 +01:00
2022-04-08 13:32:11 +02:00
**Community SDKs:**
2020-09-18 09:10:40 +02:00
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 10:05:30 +01:00
If none of the official SDKs fit your need, there's also a number of [community-developed SDKs ](https://docs.getunleash.io/reference/sdks#community-sdks ) where you might find an implementation for your preferred language (such as [Elixir ](https://gitlab.com/afontaine/unleash_ex ), [Dart ](https://pub.dev/packages/unleash ), [Clojure ](https://github.com/AppsFlyer/unleash-client-clojure ), and more).
2021-06-14 21:35:19 +02:00
2022-04-08 15:16:00 +02:00
< br / >
2022-04-06 10:48:44 +02:00
## Users of Unleash
2021-06-04 23:17:40 +02:00
2022-04-08 13:13:51 +02:00
**Unleash is trusted by thousands of companies all over the world**.
2022-04-08 13:19:02 +02:00
**Proud Open-Source users:** (send us a message if you want to add your logo here)
2016-12-02 17:47:13 +01:00
2022-04-08 13:19:02 +02:00
2017-02-25 14:26:46 +01:00
2022-04-08 15:16:00 +02:00
< br / >
2022-10-05 10:12:07 +02:00
## Migration guides
Unleash has evolved significantly over the past few years, and we know how hard it can be to keep software up to date. If you're using the current major version, upgrading shouldn't be an issue. If you're on a previous major version, check out the [Unleash migration guide ](https://docs.getunleash.io/deploy/migration_guide )!
< br / >
2022-04-08 13:13:51 +02:00
## Want to know more about Unleash?
2022-04-08 13:14:36 +02:00
### Videos and podcasts
2022-04-08 13:13:51 +02:00
- [The Unleash YouTube channel ](https://www.youtube.com/channel/UCJjGVOc5QBbEje-r7nZEa4A )
2022-06-27 10:17:44 +02:00
- [_Feature toggles — Why and how to add to your software_ — freeCodeCamp (YouTube) ](https://www.youtube.com/watch?v=-yHZ9uLVSp4&t=0s )
- [_Feature flags with Unleash_ — The Code Kitchen (podcast) ](https://share.fireside.fm/episode/zD-4e4KI+Pr379KBv )
- [_Feature Flags og Unleash med Fredrik Oseberg_ — Utviklerpodden (podcast; Norwegian) ](https://pod.space/utviklerpodden/feature-flags-og-unleash-med-fredrik-oseberg )
2022-04-08 13:13:51 +02:00
### Articles and more
- [The Unleash Blog ](https://www.getunleash.io/blog )
2022-06-27 10:17:44 +02:00
- [_Designing the Rust Unleash API client_ — Medium ](https://medium.com/cognite/designing-the-rust-unleash-api-client-6809c95aa568 )
- [_FeatureToggle_ by Martin Fowler ](http://martinfowler.com/bliki/FeatureToggle.html )
- [_Feature toggling transient errors in load tests_ — nrkbeta ](https://nrkbeta.no/2021/08/23/feature-toggling-transient-errors-in-load-tests/ )
- [_An Interview with Ivar of Unleash_ — Console ](https://console.substack.com/p/console-42 )
- [_Unleash your features gradually_ ](http://ivarconr.github.io/feature-toggles-presentation/sch-dev-lunch-2017/#1 ' ' ), slideshow/presentation by Ivar, the creator of Unleash
