mozilla
/
experimenter
зеркало из https://github.com/mozilla/experimenter.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
experimenter/.env.sample

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

64 строки
1.9 KiB
Plaintext
Исходник Постоянная ссылка Обычный вид История

Add redis to .env.sample fixes #1340 (#1526) * Add redis to .env.sample fixes #1340 * Disable json logging by default
2019-08-06 21:31:33 +03:00
BUGZILLA_API_KEY=
BUGZILLA_CC_LIST=
Simplify integration test workflow fixes #1914 (#2354) * Simplify integration test workflow fixes #1914 * Separate kill into two commands for the full stack with normandy/dc * Suppress errors from failing to remove volumes * Try again to suppress volume rm errors * Integration tests need a bugzilla host to pass * Fixed vnc up detached command * Restore and skip failing test * Update README
2020-03-17 20:35:06 +03:00
BUGZILLA_HOST=https://bugzilla.allizom.org/
add env var for worker refresh rate fixes #1739 (#2625) * add env var for worker refresh rate fixes #1739 * fixed typo * tweak Co-authored-by: Jared Lockhart <119884+jaredlockhart@users.noreply.github.com>
2020-05-07 02:52:46 +03:00
CELERY_SCHEDULE_INTERVAL=300
fixes #5803 feat(reporting): Add celery task to generate reportlogs (#5863) * fixes #5803 feat(reporting): Add celery task to generate reportlogs This commit: * adds a celery task that generates reportlogs from changelogs and normandy history Because: * This will help aggregate data for stats that will be generated
2021-07-15 22:21:35 +03:00
CELERY_REPORTING_INTERVAL=86400
fix #3707 chore(project): isolate assets to containers (#3709) Because * Recently changed the way assets are grouped I accidentally broke the way we isolate built assets to the containers This commit * Catches all built asset paths for legacy and nimbus uis and isolates them to shared volumes in the containerized dev environment
2020-10-09 16:52:59 +03:00
COMPOSE_HTTP_TIMEOUT=120
Add redis to .env.sample fixes #1340 (#1526) * Add redis to .env.sample fixes #1340 * Disable json logging by default
2019-08-06 21:31:33 +03:00
DB_HOST=db
Add project skeleton
2016-11-09 23:06:28 +03:00
DB_NAME=postgres
DB_PASS=postgres
Add redis to .env.sample fixes #1340 (#1526) * Add redis to .env.sample fixes #1340 * Disable json logging by default
2019-08-06 21:31:33 +03:00
DB_USER=postgres
DEBUG=True
DELIVERY_CONSOLE_HOST=
EMAIL_BACKEND=django.core.mail.backends.console.EmailBackend
EMAIL_HOST_PASSWORD=
EMAIL_HOST_USER=
Add remote settings to docker compose fixes #2673 (#2803) * Add remote settings to docker compose fixes #2673 * Prod uses messaging-experiments
2020-06-15 23:28:20 +03:00
EMAIL_HOST=
Add redis to .env.sample fixes #1340 (#1526) * Add redis to .env.sample fixes #1340 * Disable json logging by default
2019-08-06 21:31:33 +03:00
EMAIL_PORT=
Intent to ship email fixes #747 (#1147) * Intent to Ship Email Fixes #747 * Intent to Ship Email Part of #747 * Clean up email and code - No need to pass all these template arguments separately since they're largely available on the experiment themselves. - Do some weird stuff to try to minimize number of extra blank lines when risk/technical complexity are absent. - Disable autoescaping since this is a text email. - Add tests. * Help text should not be inside the label * Add API to send intent-to-ship email * Add front-end interface to send email * experiment_url should already include the protocol Thanks @jaredkerim for pointing this out. * Move prefetch of locales and countries to models Thanks @jaredkerim for the suggestion. * Show button only if email has not been sent Thanks @jaredkerim for the suggestion. * Just refresh the page rather than doing anything fancy Thanks @jaredkerim for the suggestion. * Fix test coverage These utility methods in the test suite do not need 100% coverage. * Send email to release drivers and experiment owner Adding a CC requires using the EmailMessage API directly instead of the send_mail wrapper. * Add setting to test configuration
2019-04-15 18:50:56 +03:00
EMAIL_RELEASE_DRIVERS=
Send experiment review email fixes #397
2018-06-06 01:34:43 +03:00
EMAIL_REVIEW=
EMAIL_SENDER=
Add redis to .env.sample fixes #1340 (#1526) * Add redis to .env.sample fixes #1340 * Disable json logging by default
2019-08-06 21:31:33 +03:00
EMAIL_SHIP=
Configuration pagination size ref #821
2019-02-14 14:41:30 +03:00
EXPERIMENTS_PAGINATE_BY=50
fix #3707 chore(project): isolate assets to containers (#3709) Because * Recently changed the way assets are grouped I accidentally broke the way we isolate built assets to the containers This commit * Catches all built asset paths for legacy and nimbus uis and isolates them to shared volumes in the containerized dev environment
2020-10-09 16:52:59 +03:00
FEATURE_ANALYSIS=False
FEATURE_MESSAGE_TYPE=False
fix #7185 chore(project): update local dev authentication for Jetstream (#7218) * fix #7185 chore(project): update local dev authentication for Jetstream * update env vars for integration; add troubleshooting tip * add gcp project access info
2022-05-04 22:07:26 +03:00
GOOGLE_APPLICATION_CREDENTIALS=/tmp/keys/application_default_credentials.json
GOOGLE_ADC_FILE=~/.config/gcloud/application_default_credentials.json
Add redis to .env.sample fixes #1340 (#1526) * Add redis to .env.sample fixes #1340 * Disable json logging by default
2019-08-06 21:31:33 +03:00
HOSTNAME=localhost
fixes #4800 feat(nimbus): implement new review flow UI against GQL backend (#5030) Because: * we want to enable the new launch experiment review flow in the UI This commit: * switches timeout to rollback to REVIEW publish status * start using real experiment data in ChangeApprovalOperations component * rework ChangeApprovalOperations to switch default state based on experiment publishState, rather than changelog events * tweaks to PageRequestReview to call real GQL mutations in response to launch review actions * refactor ChangeApprovalOperations and PageRequestReview stories to storybook v6 format, move more data into mocks shared with tests * adds a new KINTO_ADMIN_URL setting, defaulting to the production URL * exposes kintoAdminUrl in GQL config query for use by UI to open remote settings * removes the reviewApproval changelog event exposed in GQL, since it became unnecessary after another rework of ChangeApprovalOperations * adds a new TriggerCheckKintoPushQueueNow mutation to immediately trigger the check for experiments to publish to Remote Settings * adds a new SKIP_REVIEW_ACCESS_CONTROL_FOR_DEV_USER setting for disabling access control to reviews in local development
2021-04-16 01:09:13 +03:00
KINTO_ADMIN_URL=http://localhost:8888/v1/admin
Add remote settings to docker compose fixes #2673 (#2803) * Add remote settings to docker compose fixes #2673 * Prod uses messaging-experiments
2020-06-15 23:28:20 +03:00
KINTO_HOST=http://kinto:8888/v1
KINTO_PASS=experimenter
KINTO_USER=experimenter
fix #5316 feat(nimbus): make kinto timeout configurable and push to kinto immediately (#5370) Because * We'd like to be able to push to kinto immediately after approving a launch/change/end * We need to be able to evaluate a timeout separately from the time since the last push happened This commit * Uses the time since the last change was made to determine whether a kinto change should time out * Pushes to kinto immediately after approving instead of waiting for the next scheduled task run * Introduces published_dto_changed to NimbusChangeLog to be able to distinguish live updates from live rejections * Removes the 0170 data migration tests because they only pass if 0170 is the most recent migration
2021-06-04 20:39:14 +03:00
KINTO_REVIEW_TIMEOUT=60
Implement most trivial rules from our quality standards (#9711) Because - We are trying to promote [Quality Standards](https://mozilla.github.io/syseng-pod/quality-standards/) across Mozilla's repositories - Experimenter has a [very good score already](https://mozilla.github.io/syseng-pod/quality-standards/#service-Experimenter) This PR - Implements a few of the harmless ones to improve even the score :) --------- Co-authored-by: Jared Lockhart <119884+jaredlockhart@users.noreply.github.com> Co-authored-by: Yashika Khurana <yashikakhuranayashika@gmail.com>
2023-11-10 04:18:05 +03:00
LOG_LEVEL=INFO
Add redis to .env.sample fixes #1340 (#1526) * Add redis to .env.sample fixes #1340 * Disable json logging by default
2019-08-06 21:31:33 +03:00
LOGGING_USE_JSON=False
Add Normandy Recipe info fixes #498 (#1146)
2019-04-18 19:14:30 +03:00
NORMANDY_API_HOST=
fix #3914 fix(legacy): Change DC links and buttons to NDT web (#3946) * fix #3914 fix(legacy): Change DC links and buttons to NDT web Because * NDT is the preferred way to view recipes This commits * Swaps DC related things to NDT things * Introduces new environment variables: EXPERIMENTER_INSTANCE and NORMANDY_DEVTOOLS_HOST * changed up environment variables * changed env vars to include instance * hide web button when extension exists
2020-11-20 22:54:41 +03:00
NORMANDY_DEVTOOLS_HOST=https://normandy-devtools.services.mozilla.com/#/local
Add redis to .env.sample fixes #1340 (#1526) * Add redis to .env.sample fixes #1340 * Disable json logging by default
2019-08-06 21:31:33 +03:00
OPENIDC_CLIENT_ID=
OPENIDC_CLIENT_SECRET=
OPENIDC_HEADER=HTTP_X_FORWARDED_USER
REDIS_DB=0
REDIS_HOST=redis
REDIS_PORT=6379
SECRET_KEY=SOMETHINGSECURE
SENTRY_DSN=
fix #4210 chore(nimbus): use separate sentry dsn for nimbus ui (#5080) Because * We'd like to track Nimbus UI as a separate Sentry project This commit * Adds a second Sentry DSN just for Nimbus UI
2021-04-21 23:47:57 +03:00
SENTRY_DSN_NIMBUS_UI=
fixes #4800 feat(nimbus): implement new review flow UI against GQL backend (#5030) Because: * we want to enable the new launch experiment review flow in the UI This commit: * switches timeout to rollback to REVIEW publish status * start using real experiment data in ChangeApprovalOperations component * rework ChangeApprovalOperations to switch default state based on experiment publishState, rather than changelog events * tweaks to PageRequestReview to call real GQL mutations in response to launch review actions * refactor ChangeApprovalOperations and PageRequestReview stories to storybook v6 format, move more data into mocks shared with tests * adds a new KINTO_ADMIN_URL setting, defaulting to the production URL * exposes kintoAdminUrl in GQL config query for use by UI to open remote settings * removes the reviewApproval changelog event exposed in GQL, since it became unnecessary after another rework of ChangeApprovalOperations * adds a new TriggerCheckKintoPushQueueNow mutation to immediately trigger the check for experiments to publish to Remote Settings * adds a new SKIP_REVIEW_ACCESS_CONTROL_FOR_DEV_USER setting for disabling access control to reviews in local development
2021-04-16 01:09:13 +03:00
SKIP_REVIEW_ACCESS_CONTROL_FOR_DEV_USER=true
Add redis to .env.sample fixes #1340 (#1526) * Add redis to .env.sample fixes #1340 * Disable json logging by default
2019-08-06 21:31:33 +03:00
STATSD_BACKEND=markus.backends.logging.LoggingMetrics
STATSD_HOST=
STATSD_PORT=
STATSD_PREFIX=experimenter
fix #6422 fix #6243 feat(nimbus): add NimbusBranchScreenshot model and configure file storage (#6425) Because: * we want to store screenshots associated with branches This commit: * adds a new NimbusBranchScreenshot model to store & manage screenshots associated with an experiment branch * adds migration to add new NimbusBranchScreenshot model * adds Pillow dependency required by Django ImageField in model * adds UPLOADS_GS_CREDENTIALS and UPLOADS_GS_BUCKET_NAME env vars for Google Cloud credentials file path and bucket name for image storage * uses FileSystemStorage defaulting to MEDIA_ROOT and MEDIA_URL if UPLOADS_GS_CREDENTIALS is not supplied, switches to GoogleCloudStorage if credentials are configured * adds NimbusBranchAdmin with NimbusBranchScreenshotInlineAdmin to manage branch screenshots in Django admin
2021-09-14 23:31:54 +03:00
UPLOADS_GS_BUCKET_NAME=
chore(project): switch to STORAGES setting for storage providers (#11193) Because * We need to use different storage providers for local dev, tests, and in prod * We used to configure this by using a custom function that called get_storage_class * However get_storage_class is depcated in Django 5.1 * We need to switch to using the STORAGES setting This commit * Removes the old storage setting code * Adds STORAGES to settings.py * Updates tests as necessary fixes #11192
2024-08-20 00:00:26 +03:00
UPLOADS_FILE_STORAGE=django.core.files.storage.FileSystemStorage
fix #9501 feat(cirrus): update variables prefix (#9504) Because - ENV variables are being used in cirrus, It is easy to check the set values if all start with Prefix `CIRRUS_` - sets the app id and channel from the config for glean initialization This commit - Adds a prefix to all .env variables - Update glean config to use app id and channel correctly fixes #9501
2023-09-27 20:07:33 +03:00
CIRRUS_REMOTE_SETTING_REFRESH_RATE_IN_SECONDS=10
CIRRUS_REMOTE_SETTING_URL=http://kinto:8888/v1/buckets/main/collections/nimbus-web-experiments/records
test(cirrus): Cirrus preview flag (#11167) Because - We added preview flag support for Cirrus to enable them to QA This commit - Add a new test to test preview flag functionality Fixes #11103 Note: Working on to send it to main collection
2024-08-26 18:56:27 +03:00
CIRRUS_REMOTE_SETTING_PREVIEW_URL=http://kinto:8888/v1/buckets/main-workspace/collections/nimbus-web-preview/records
fix #9501 feat(cirrus): update variables prefix (#9504) Because - ENV variables are being used in cirrus, It is easy to check the set values if all start with Prefix `CIRRUS_` - sets the app id and channel from the config for glean initialization This commit - Adds a prefix to all .env variables - Update glean config to use app id and channel correctly fixes #9501
2023-09-27 20:07:33 +03:00
CIRRUS_APP_ID=demo-app-beta
CIRRUS_APP_NAME=demo_app
CIRRUS_CHANNEL=beta
fix #9377 feat(cirrus): Configure sentry for stage and prod environment for cirrus (#9378) Because - We want to monitor errors for both stage and prod for cirrus consuming applications This commit - We have two new projects setup on sentry [cirrus-prod](https://mozilla.sentry.io/projects/cirrus-prod/?project=4505841055825920) and [cirrus-stage](https://mozilla.sentry.io/projects/cirrus-stage/?project=4505841048682496) - Add sentry sdk to Cirrus - Consuming application needs to pass the DSN value as part of environment variables - Updated docs - Tested manually sentry error- [manually created error to test the integration](https://mozilla.sentry.io/issues/4463061449/?project=4505841048682496&query=&referrer=project-issue-stream) fixes #9377
2023-09-11 19:53:04 +03:00
CIRRUS_FML_PATH=./feature_manifest/sample.yml
fix #9501 feat(cirrus): update variables prefix (#9504) Because - ENV variables are being used in cirrus, It is easy to check the set values if all start with Prefix `CIRRUS_` - sets the app id and channel from the config for glean initialization This commit - Adds a prefix to all .env variables - Update glean config to use app id and channel correctly fixes #9501
2023-09-27 20:07:33 +03:00
CIRRUS_SENTRY_DSN=
feat(cirrus): Add instance metric (#9920) Because - We want to tie metrics to actual container logs which can be sent at a startup and configurable This commit - Add new metrics for startup Fixes #9911 --------- Co-authored-by: Barret Rennie <barret@brennie.ca>
2023-12-19 20:42:06 +03:00
CIRRUS_INSTANCE_NAME=
feat(cirrus): Configure sentry for different projects (#10045) Because - We are using Sentry for all the Cirrus implementing applications such as Monitor, VPN, and so on...... Currently, it is hard to track where the error is coming from until we see the issue in detail. This commit - Sentry supports the concept of environment, so in the same project you can configure different environment - By default, Sentry uses a `production` environment, so the default value used in initialization is `production` - Add support for using environment so that the `cirrus-stage` project can have `monitor-stage` and `vpn-stage` and similarly `cirrus-prod` can have `monitor-prod` and `vpn-prod` environments. Note: Sentry [environment](https://docs.sentry.io/product/sentry-basics/concepts/environments/) selection also makes it easy to filter the issues, for example ![image](https://github.com/mozilla/experimenter/assets/25848231/34f7dd90-c19a-4c5d-9541-9fb8168167ea) Fixes #9999
2024-01-15 21:55:08 +03:00
CIRRUS_ENV_NAME=test_instance_stage
feat(cirrus): Set glean max event buffer value (#10070) Because - When setting up glean sdk on cirrus side, we set the maxEvents to 500, which means it waits on the client side to gather all 500 events, and once it gets 500 then it sends the batch of events. Implementing applications should be able to adjust the value that works best for them. This commit - Add the option to set no. of events to store in buffer through `.env`, by default it uses `10` now Fixes #9534
2024-01-22 23:42:38 +03:00
CIRRUS_GLEAN_MAX_EVENTS_BUFFER=20