-
Notifications
You must be signed in to change notification settings - Fork 18
/
env-example
110 lines (82 loc) · 3.01 KB
/
env-example
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
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
# This is a placeholder file for the environment variables you'll need to
# configure for your application.
#
# - Make a copy and name it something appropriate.
# - e.g. .azure-env
# - Fill in the values.
# - Load the values into your environment before interacting with Azure:
#
# $ # Export values from file into environment:
# $ export $(grep -v '^#' .azure-env | xargs)
# $ # Now interact with (e.g.) the production PosgreSQL instance:
# $ ./manage.py showmigrations
# ...
# The Azure Resource Group and Location to use for you applicaiton.
# - If using the VS Code App Service extension to create your app,
# use the values it provides
AZ_GROUP=''
AZ_LOCATION=''
# The name you choose for your App Service application.
APP_SERVICE_APP_NAME=''
# Server Name, Admin User and Admin Password for creating the Azure
# PostgreSQL server.
POSTGRES_SERVER_NAME=''
POSTGRES_ADMIN_USER=''
POSTGRES_ADMIN_PASSWORD=''
# The Azure PostgreSQL server host.
# This will not be available until after creating the database server.
# (Will be output at end if running `./bin/createdb.py`)
POSTGRES_HOST=''
# The application DB name you want to use.
# `./bin/createdb.py` will offer to create this db after creating the server.
APP_DB_NAME=''
# The production settings module. `tutorial.azure` is the example provided.
DJANGO_SETTINGS_MODULE='tutorial.azure'
# Azure Storages Account Name, Container Name and Key for staticfiles.
# Once these are set you can run collectstatic to push the staticfiles.
AZ_STORAGE_ACCOUNT_NAME=''
AZ_STORAGE_KEY=''
AZ_STORAGE_CONTAINER=''
# App Service Deployment Settings for Azure Pipeline
#
# Combine these to give the push URL:
#
# "https://$DEPLOYMENT_USERNAME:$DEPLOYMENT_PASSWORD@$DEPLOYMENT_URL"
#
# git push -f <URL> HEAD:master
#
# $ git push -f "https://$DEPLOYMENT_USERNAME:$DEPLOYMENT_PASSWORD@$DEPLOYMENT_URL" HEAD:master
#
# Credentials can be added as secret variable to Azure DevOps Pipelines in order to use `.azure-deploy.yml`.
#
#
# Username and Password for the deployment.
#
# YOU MUST CREATE THESE DEPLOY THE DEPLOYMENT URL WILL BE AVAILABLE.
#
# Create by using the `az` CLI:
#
# $ az webapp deployment user set --user-name <username> --password <password>
#
# Or add in the portal.
#
# App > Deployment Center > Deployment Credentials > User Credentials
DEPLOYMENT_USERNAME=''
DEPLOYMENT_PASSWORD=''
# The `LocalGit` deployment URL of the App.
#
# You get this when the deployment source is configured.
# You can retrieve it from the portal or via the `az` CLI:
#
# $ az webapp deployment source config-local-git --name=<APP_SERVICE_APP_NAME> --resource-group=<AZ_GROUP>
DEPLOYMENT_URL=''
# Extra variables for deploying the Functions version of the app.
#
# - Resource Group for the functions application.
# - Functions application name.
FUNCTIONS_GROUP=''
FUNCTIONS_APP_NAME=''
# Base URL of the function wrapping requests to django.
# This is used for correctly mapping static asset URLs.
# The example application uses `api/serverless`.
FUNCTIONS_MOUNT_POINT='api/serverless'