You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(docker): Run experimentation on the Flagsmith Postgres database in docker compose - #8884
The API now stores SDK events in its own Postgres, so docker compose no longer needs a separate experimentation stack.
Drop Kafka, ClickHouse, the ingestion server and warehouse delivery from docker-compose.yml; experimentation stays enabled.
Remove docker-compose.flags-only.yml and the flags-only Makefile switch.
Update the Docker hosting guide: pick Flagsmith database under Environment Settings > Warehouse to try out experimentation; production should use a dedicated warehouse.
How did you test this code?
Built the image from this branch and ran the compose file from a fresh volume, then in the dashboard: onboarding, enabled the Flagsmith database warehouse, sent a test event, created a metric and experiment. Sent exposures and purchases for 60 identities; results and exposure charts rendered per variant.
The Makefile now uses Docker Compose’s default file selection. The flags-only Compose file and the experimentation services in the main Compose file were removed. EXPERIMENTATION_ENABLED remains set to 'true', and the warehouse credential value is now literal. The Docker guide removes the flags-only instructions and describes using the Flagsmith database to store experimentation events in PostgreSQL.
Document the upgrade path and dedicated-warehouse delivery requirements before merging. Existing installations can retain unusable warehouse connections, while users following the production guidance can configure a warehouse that receives no events.
- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
github-actions
Bot
added
feature
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature.Changes
Contributes to #8864
The API now stores SDK events in its own Postgres, so docker compose no longer needs a separate experimentation stack.
docker-compose.yml; experimentation stays enabled.docker-compose.flags-only.ymland theflags-onlyMakefile switch.How did you test this code?
Built the image from this branch and ran the compose file from a fresh volume, then in the dashboard: onboarding, enabled the Flagsmith database warehouse, sent a test event, created a metric and experiment. Sent exposures and purchases for 60 identities; results and exposure charts rendered per variant.