chore/archive repo (#19)
Ben Rometsch
1 year ago
committed by
GitHub
parent
98b9d2625b
commit
4b247ab5c9
@ -1,38 +1,3 @@
|
||||
[](https://www.flagsmith.com/)
|
||||
> :warning: Our self-hosted repo has been archived!
|
||||
|
||||
[Flagsmith](https://www.flagsmith.com/) is an open source, fully featured, Feature Flag and Remote Config service. Use
|
||||
our hosted API, deploy to your own private cloud, or run on-premise.
|
||||
|
||||
# Flagsmith
|
||||
|
||||
Flagsmith makes it easy to create and manage features flags across web, mobile, and server side applications. Just wrap
|
||||
a section of code with a flag, and then use Flagsmith to toggle that feature on or off for different environments, users
|
||||
or user segments.
|
||||
|
||||
Get up and running in 1 minute with:
|
||||
|
||||
```bash
|
||||
git clone git@github.com:flagsmith/self-hosted.git
|
||||
docker-compose -f self-hosted/docker-compose.yml up
|
||||
```
|
||||
|
||||
[](https://www.flagsmith.com/)
|
||||
|
||||
## Features
|
||||
|
||||
- **Feature flags**. Release features with confidence through phased rollouts.
|
||||
- **Remote config**. Easily toggle individual features on and off, and make changes without deploying new code.
|
||||
- **A/B and Multivariate Testing**. Use segments to run A/B and multivariate tests on new features. With segments, you
|
||||
can also introduce beta programs to get early user feedback.
|
||||
- **Organization Management**. Organizations, projects, and roles for team members help keep your deployment organized.
|
||||
- **Integrations**. Easily enhance Flagsmith with your favourite tools.
|
||||
|
||||
## Getting Started
|
||||
|
||||
For full documentation visit [https://docs.flagsmith.com/deployment/docker](https://docs.flagsmith.com/deployment/docker).
|
||||
|
||||
## Resources
|
||||
|
||||
- [Website](https://www.flagsmith.com/)
|
||||
- [Documentation](https://docs.flagsmith.com/)
|
||||
- If you have any questions about our projects you can email [support@flagsmith.com](mailto:support@flagsmith.com)
|
||||
We've moved our docker-compose over to our [monorepo](https://github.com/Flagsmith/flagsmith/tree/main/docker-compose.yml).
|
||||
|
||||
@ -1,71 +0,0 @@
|
||||
# See https://docs.flagsmith.com/deployment/docker for more information on running Flagsmith in Docker
|
||||
# This will docker-compose file will run the entire Flagsmith Platform in Docker
|
||||
|
||||
version: "3"
|
||||
|
||||
volumes:
|
||||
pgdata:
|
||||
|
||||
|
||||
services:
|
||||
postgres:
|
||||
image: postgres:11.12-alpine
|
||||
environment:
|
||||
POSTGRES_PASSWORD: password
|
||||
POSTGRES_DB: flagsmith
|
||||
container_name: flagsmith_postgres
|
||||
volumes:
|
||||
- pgdata:/var/lib/postgresql/data
|
||||
|
||||
flagsmith:
|
||||
image: flagsmith/flagsmith:latest
|
||||
environment:
|
||||
# All environments variables are available here:
|
||||
# API: https://docs.flagsmith.com/deployment/locally-api#environment-variables
|
||||
# UI: https://docs.flagsmith.com/deployment/locally-frontend#environment-variables
|
||||
|
||||
DATABASE_URL: postgresql://postgres:password@postgres:5432/flagsmith
|
||||
USE_POSTGRES_FOR_ANALYTICS: "true" # Store API and Flag Analytics data in Postgres
|
||||
|
||||
ENV: prod # set to "prod" in production.
|
||||
DJANGO_ALLOWED_HOSTS: "*" # Change this in production
|
||||
ALLOW_ADMIN_INITIATION_VIA_CLI: "true" # Change this in production
|
||||
FLAGSMITH_DOMAIN: "localhost:8000" # Change this in production
|
||||
DJANGO_SECRET_KEY: "secret" # Change this in production
|
||||
# PREVENT_SIGNUP: "true" # Uncomment to prevent additional signups
|
||||
# ENABLE_ADMIN_ACCESS_USER_PASS: "true" # set to "true" to enable access to the /admin/ Django backend via your username and password
|
||||
# ALLOW_REGISTRATION_WITHOUT_INVITE: "true"
|
||||
|
||||
# Enable Task Processor
|
||||
TASK_RUN_METHOD: TASK_PROCESSOR # other options are: SYNCHRONOUSLY, SEPARATE_THREAD (default)
|
||||
# For more info on configuring E-Mails - https://docs.flagsmith.com/deployment/locally-api#environment-variables
|
||||
#
|
||||
# Example SMTP:
|
||||
# EMAIL_BACKEND: django.core.mail.backends.smtp.EmailBackend
|
||||
# EMAIL_HOST: mail.example.com
|
||||
# SENDER_EMAIL: flagsmith@example.com
|
||||
# EMAIL_HOST_USER: flagsmith@example.com
|
||||
# EMAIL_HOST_PASSWORD: smtp_account_password
|
||||
# EMAIL_PORT: 587 # optional
|
||||
# EMAIL_USE_TLS: "true" # optional
|
||||
|
||||
ports:
|
||||
- "8000:8000"
|
||||
depends_on:
|
||||
- postgres
|
||||
links:
|
||||
- postgres
|
||||
|
||||
# The flagsmith_processor service is only needed if TASK_RUN_METHOD set to TASK_PROCESSOR
|
||||
# in the application environment
|
||||
flagsmith_processor:
|
||||
image: flagsmith/flagsmith:latest
|
||||
environment:
|
||||
DATABASE_URL: postgresql://postgres:password@postgres:5432/flagsmith
|
||||
USE_POSTGRES_FOR_ANALYTICS: "true"
|
||||
depends_on:
|
||||
- flagsmith
|
||||
- postgres
|
||||
links:
|
||||
- postgres
|
||||
command: run-task-processor
|
||||
Loading…
Reference in new issue