-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add specific use cases #174
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, love all the changes. Added some thoughts / corrections.
## Database Support | ||
|
||
Flipt's plugable data store architecture allows it to be deployed to a variety of edge computing environments without requiring traditional server-based relational databases. Specifically, Flipt's support for SQLite, [LibSQL](https://turso.tech/libsql), and [Turso](https://turso.tech/) allow it to run in environments where a traditional database is not available. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could additionally add that the same goes for the declarative backends. They allow you to deploy Flipt to edge locations, much like putting a CDN infront of an s3 bucket. You can deploy Flipt infront of object storage and evaluate at the edge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah i moved the section on declarative storage up and put them both under the same heading
usecases/gitops.mdx
Outdated
|
||
Our [GitHub Action](/tooling/github-actions) allows you to easily integrate Flipt into your CI/CD pipelines. This allows you to install Flipt into your CI pipeline and run tests against your feature flags before deploying your code to production. | ||
|
||
You can also import your feature flag data from your repository, or any other source, into Flipt using our [Import Command](/cli/commands/import). This allows you to import your feature flag data into Flipt before running your tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is better to encourage folks to use local
backend here for CI. As it avoid the need to run Flipt with a DB and have a separate import
step. You just run Flipt with local
and point it at the relevant directory.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not both? updated
Co-authored-by: Yoofi Quansah <[email protected]>
Co-authored-by: George <[email protected]>
Co-authored-by: Yoofi Quansah <[email protected]>
Co-authored-by: George <[email protected]>
Co-authored-by: George <[email protected]>
Co-authored-by: George <[email protected]>
Adds more specific use cases where Flipt is uniquely applicable including: