-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathtemplate.env
More file actions
94 lines (72 loc) · 2.87 KB
/
template.env
File metadata and controls
94 lines (72 loc) · 2.87 KB
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
91
92
93
94
#
# Template.env
#
# When running the app locally, this file should be copied to .env
#
# This is a long, unique string of characters that is used for Django's cryptographic signing
SECRET_KEY=
# A list of domains and/or IPs that Django is allowed to serve
DJANGO_ALLOWED_HOSTS=localhost 127:0.0.1 [::1]
# A python path for the settings module that Django should use
# When running in production, this value should be set to: app.setting.production
# See: https://docs.djangoproject.com/en/3.1/topics/settings/#envvar-DJANGO_SETTINGS_MODULE
DJANGO_SETTINGS_MODULE=app.settings.dev
# The port on which the application should listen
SERVER_PORT=8000
#
# Database Configuration
#
# The Django module used for managing the database connection.
# If not provided, Django will default to SQLite
SQL_ENGINE=django.db.backends.postgresql
# The name of the database (or, for sqlite, the name of the file) that Django should use
# I not provided, it defaults to db.sqlite3
SQL_DATABASE=
# The username used to authenticate with the database
# defaults to "user"
SQL_USER=
# The password used to authenticate with the database
# defaults to "password"
SQL_PASSWORD=
# The hostname used to connect to the database
# defaults to "localhost"
SQL_HOST=db
# The port on which the database is listening
# defaults to 5432
SQL_PORT=5432
# A flag for the entrypoint.sh script
# If this value is "postgres", the script will wait for the database to be available before running the app
DATABASE=postgres
#
# Superuser Configuration
#
# When starting up the Django process, a superuser with full access to the admin will be created.
# When running in production, make sure that these are secure values
#
# This will be the superuser login name
DJANGO_SUPERUSER_USERNAME=
# This will be the superuser password
DJANGO_SUPERUSER_PASSWORD=
# This will be the email account associated with the Superuser
DJANGO_SUPERUSER_EMAIL=
#
# Algolia Configuration
#
# Most of these details can be found under the "API Keys" in the Algolia Dashboard
#
# The ID of the Algolia application that owns the index and API key used here, typically a 10-character string.
ALGOLIA_APP_ID=
# The ID of the Algolia index that will be used. This should be owned by the account associated with the APP_ID above
# It is strongly recommended to use different indices for development, production, and testing
ALGOLIA_INDEX=
# A secured API Key created on Algolia.
# This key should have the browse, addObject, deleteObject, and deleteIndex permissions for the index specified above.
#
#NOTE: THIS SHOULD NOT BE AN ADMIN KEY.
# See: https://www.algolia.com/doc/guides/security/api-keys/
ALGOLIA_API_KEY=
# This overides the default URL for static files included in the Django admin templates.
# This should be used to include the S3 bucket URL that we are using to store the static files.
# For local development purposes this can be left commented out.
#
# STATIC_URL=