-
Notifications
You must be signed in to change notification settings - Fork 18
/
env_dist
90 lines (79 loc) · 4.52 KB
/
env_dist
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
# NOTE: env-dist is a sample .env file distributed with lookit-api for local development. To USE these settings, copy
# them to a file named .env and make any changes needed.
# Run in DEBUG mode locally. This gives access to the Django debug toolbar among other things. (Note that if DEBUG is
# false, some different choices are made in settings.py; you may want to review those and ensure you have the relevant
# dependencies installed.)
DEBUG=True
# Site settings
ALLOWED_HOSTS=localhost
BASE_URL=https://localhost:8000
CORS_ORIGIN_ALLOW_ALL=True
ENVIRONMENT=develop
EXPERIMENT_BASE_URL=https://localhost:4200
SITE_DOMAIN=localhost:8000
SITE_NAME=Lookit
# GCP settings for building/deploying studies; bundling video; bundling data downloads. Leave
# GOOGLE_APPLICATION_CREDENTIALS blank or don't define to skip using. If you need to test functionality involving
# uploading files to Google Cloud storage, you can create a project with two buckets: GS_BUCKET_NAME for experiment
# builds, and GS_PRIVATE_BUCKET_NAME for data/video files. Provide the full path to a .json credentials file as
# GOOGLE_APPLICATION_CREDENTIALS.
GOOGLE_APPLICATION_CREDENTIALS=
GS_BUCKET_NAME=
GS_PRIVATE_BUCKET_NAME=
GS_PROJECT_ID=
# Directory in which to (locally) build experiments before sending to GCP
EXPERIMENT_LOCATION=experiments
# Settings for participant video storage. To actually access video locally, you would also need to
# (1) Run ember-lookit-frameplayer locally and configure it to send video to Lookit's dev environment on Pipe, or to
# your own Pipe account
# (2) Create (if using your own Pipe account) or request (if using Lookit's) a webhook on the Pipe dev environment to
# hit your local lookit-api server's /exp/renamevideo, which you can expose e.g. using ngrok. A webhook key is used
# by lookit-api to authenticate requests from Pipe upon completing video upload. Get this value from your Pipe
# account or request from Lookit if using Lookit's dev environment on Pipe and set PIPE_WEBHOOK_KEY below.
# (3) Create (if using your own Pipe account and sending video to your own S3 bucket) or request (if using Lookit's
# Pipe account and sending video to the Lookit dev bucket) AWS credentials to be able to access the bucket, and set
# them up locally on your system using the AWS command line tools. Set the BUCKET_NAME to your bucket.
BUCKET_NAME=
PIPE_WEBHOOK_KEY=
# AWS S3 settings for participant video storage. This is used when the study uses RecordRTC/S3 for participant webcam recordings, rather than Pipe.
S3_REGION=
S3_ACCESS_KEY_ID=
S3_SECRET_ACCESS_KEY=
S3_BUCKET=
AWS_LAMBDA_SECRET_ACCESS_KEY=
# jsPsych S3 settings for participant video storage. This is used for video uploading by lookit-jspsych during jsPsych studies.
JSPSYCH_S3_REGION=
JSPSYCH_S3_ACCESS_KEY_ID=
JSPSYCH_S3_SECRET_ACCESS_KEY=
JSPSYCH_S3_BUCKET=
# Default repo and branch to use for experiment runner
EMBER_EXP_PLAYER_BRANCH=master
EMBER_EXP_PLAYER_REPO=https://github.com/lookit/ember-lookit-frameplayer
# RabbitMQ settings. Only change if you have configured rabbitmq differently yourself.
RABBITMQ_HOST=localhost
RABBITMQ_PASSWORD=admin
RABBITMQ_PORT=5672
RABBITMQ_USERNAME=lookit-admin
RABBITMQ_VHOST=/
# PostgreSQL settings. By default Postgres is configured to have a superuser called postgres with no password.
# If you want to use a different user, or if you have configured a password for the postgres user, set it here.
# To check these credentials, you can run `psql --db <DB_NAME> --user <DB_USER>` at the command line and make sure
# you can log in using DB_PASSWORD.
DB_NAME=lookit
DB_HOST=127.0.0.1
DB_PASSWORD=postgres
DB_PORT=5432
DB_USER=postgres
# Email settings for emails to researchers/participants. By default we just print "emails" to the console. To use
# smtp instead, you would also define EMAIL_HOST_USER and EMAIL_HOST_PASSWORD. The EMAIL_BACKEND is selected in
# settings.py: django.core.mail.backends.console.EmailBackend in DEBUG mode otherwise SendGrid, so we don't set it here
# explicitly.
# If you want to run the SendGrid email backend locally, add an API key. Find where the certs are by running
# python -m certifi from the lookit-api pipenv shell, then put that path under SSL_CERT_FILE and REQUESTS_CA_BUNDLE
# to avoid errors where a local certificate file is not found upon making the request.
# SENDGRID_API_KEY=SG.KEY-HERE
# SSL_CERT_FILE=/path/to/cacert.pem
# REQUESTS_CA_BUNDLE=/path/to/cacert.pem
# Google tag manager. You will have to goto https://tagmanager.google.com/ to find the ID.
GOOGLE_TAG_MANAGER_ID=