There are two ways to configure Flipt: using a configuration file or through environment variables.
The default way that Flipt is configured is with the use of a configuration file default.yml.
This file is read when Flipt starts up and configures several important properties for the server.
You can edit any of these properties to your liking, and on restart Flipt will pick up the new changes.
These defaults are commented out in default.yml to give you an idea of what they are. To change them you'll first need to uncomment them.
These properties are as follows:
|Level at which messages are logged (trace, debug, info, warn, error, fatal, panic)||info|
|File to log to instead of STDOUT||v0.10.0|
|Enable UI and API docs||true|
|Enable CORS support||false||v0.7.0|
|Sets Access-Control-Allow-Origin header on server||"*" (all domains)||v0.7.0|
|Enable tracing support with Jaeger||false||v0.17.0|
|The UDP host destination to report spans||localhost||v0.17.0|
|The UDP port destination to report spans||6831||v0.17.0|
|Enable check for newer versions of Flipt on startup||true||v0.17.0|
|Enable anonymous telemetry data (see Telemetry)||true||v1.8.0|
|Directory on the host to store local state||v1.8.0|
|The host address on which to serve the Flipt application||0.0.0.0|
|The HTTP port on which to serve the Flipt REST API and UI||8080|
|The HTTPS port on which to serve the Flipt REST API and UI||443||v0.8.0|
|The port on which to serve the Flipt GRPC server||9000|
|Path to the certificate file (if protocol is set to ||v0.8.0|
|Path to the certificate key file (if protocol is set to ||v0.8.0|
|Enable in-memory caching||false|
|Duration at which cache items are considered expired||-1 (none)||v0.12.0|
|Interval at which expired items are evicted from the cache||10m (10 minutes)||v0.12.0|
|URL to access Flipt database||file:/var/opt/flipt/flipt.db|
|Protocol (Sqlite, MySQL, Postgres) for Flipt database (URL takes precedence)||v0.18.0|
|Host to access Flipt database (URL takes precedence)||v0.18.0|
|Port to access Flipt database (URL takes precedence)||v0.18.0|
|Name of Flipt database (URL takes precedence)||v0.18.0|
|User to access Flipt database (URL takes precedence)||v0.18.0|
|Password to access Flipt database (URL takes precedence)||v0.18.0|
|The maximum number of connections in the idle connection pool||2||v0.17.0|
|The maximum number of open connections to the database||unlimited||v0.17.0|
|Sets the maximum amount of time in which a connection can be reused||unlimited||v0.17.0|
|Where the Flipt database migration files are kept||/etc/flipt/config/migrations|
All options in the configuration file can be overridden using environment variables using the syntax:
Using environment variables to override defaults is especially helpful when running with Docker as described in the Installation documentation.
Everything should be upper case,
. should be replaced by
_. For example, given these configuration settings:
You can override them using:
SQLite is enabled by default for simplicity, however you should use Postgres or MySQL if you intend to run multiple copies of Flipt in a high availability configuration.
The database connection can be configured as follows:
# file: informs flipt to use SQLite
The Postgres database must exist and be up and running before Flipt will be able to connect to it.
The MySQL database must exist and be up and running before Flipt will be able to connect to it.
From time to time the Flipt database must be updated with new schema. To accomplish this, Flipt includes a
migrate command that will run any pending database migrations for you.
If Flipt is started and there are pending migrations, you will see the following error in the console:
migrations pending, please backup your database and run `flipt migrate`
If it is your first run of Flipt, all migrations will automatically be run before starting the Flipt server.
You should backup your database before running
flipt migrate to ensure that no data is lost if an error occurs during migration.
If running Flipt via Docker, you can run the migrations in a separate container before starting Flipt by running:
docker run -it markphelps/flipt:latest /bin/sh -c './flipt migrate'
Flipt supports importing and exporting your feature flag data since v0.13.0.
To import previously exported Flipt data, use the
flipt import command. You can import either from a file or from STDIN.
To import from STDIN, Flipt requires the
cat flipt.yaml | flipt import --stdin
If not importing using
--stdin, Flipt requires the file to be imported as an argument:
flipt import flipt.yaml
This command supports the
--drop flag that will drop all of the data in your Flipt database tables before importing. This is to ensure that no data collisions occur during the import.
Be careful when using the
--drop flag as it will immediately drop all of your data and there is no undo. It is recommend to first backup you database before running this command just to be safe.
To export Flipt data, use the
flipt export command.
export will output to STDOUT:
$ flipt export
- key: new-contact-page
name: New Contact Page
description: Show users our Beta contact page
- key: blue
- key: green
You can also export to a file using the
-o filename or
--output filename flags:
flipt export -o flipt.yaml
Flipt supports an in-memory cache to enable faster reads and evaluations. Enabling in-memory cache has been shown to speed up read performance by several orders of magnitude.
Enabling in-memory caching when running more than one instance of Flipt is not advised as it may lead to unpredictable results.
Caching works as follows:
- All reads go through the cache
- All writes flush the entire cache to ensure the cache is kept up to date
- A cache miss will fetch the item from the database and add the item to the cache for the next read
- A cache hit will simply return the item from the cache, not interacting with the database
To enable caching set the following in your config:
You can also configure an optional duration at which items in the cache are marked as expired.
For example, if you set the cache expiration to
5m, items that have been in the cache for longer than 5 minutes will be marked as expired, meaning the next read for that item will hit the database.
Setting an eviction interval will automatically remove expired items from your cache at a defined period.
The combination of cache expiration and eviction can help lessen the amount of memory your cache uses, as infrequently accessed items will be removed over time.
To tune the expiration and eviction interval of the cache set the following in your config:
expiration: 5m # items older than 5 minutes will be marked as expired
eviction_interval: 2m # expired items will be evicted from the cache every 2 minutes
Flipt developers rely on anonymous usage data to help prioritize new features and improve the product. The information collected is completely anonymous, never shared with external entities, and you can opt out at any time.
What Kind of Data is Collected?
- Flipt version
You can view the full schema of the telemetry data on GitHub.
We use Segment to collect the data. Only the creator of Flipt has access to the data.
How to Disable Telemetry
There are multiple ways in which you can disable telemetry collection:
Flipt exposes Prometheus metrics at the
/metrics HTTP endpoint. To see which metrics are currently supported, point your browser to
You should see a bunch of metrics being recorded such as:
There is an example provided in the GitHub repository showing how to setup Flipt with Prometheus.
There is an example provided in the GitHub repository showing how to setup Flipt with Jaeger.
There is currently no built in authentication, authorization or encryption as Flipt was designed to work inside your trusted architecture and not be exposed publicly. If you wish to expose the Flipt dashboard and REST API publicly using HTTP Basic Authentication, you can do so by using a reverse proxy.
There is an example provided in the GitHub repository showing how this can work.