-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
37 lines (31 loc) · 1.41 KB
/
.env.example
File metadata and controls
37 lines (31 loc) · 1.41 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
# whenever you change any of these, you likely have to restart the server
# (and just to be safe, if applicable, the client/ `npm start` server too)
# hostname of backend server; format like 'http://localhost' (no port or slash)
HOST_NAME=
# port to listen on; set BACKEND_PORT to this in client/.env when developing with client/ $ npm start
PORT=
# 'development' if developing with client/ $ npm start, 'production' otherwise
NODE_ENV=
# required if NODE_ENV=development, ignored otherwise; this is the hostname:port
# serving the frontend; port is the PORT you set in client/.env; e.g. 'http://localhost:8888'
FRONTEND_ADDRESS=
# from spotify developer dashboard
CLIENT_ID=
# from spotify developer dashboard
CLIENT_SECRET=
# spotify account id of account that owns all the playlists
OWNER_ACCOUNT_ID=
# refresh token for the owner account
OWNER_ACCOUNT_REFRESH_TOKEN=
# passcode for making admin requests to server, must include in cookie 'admin_key'
ADMIN_KEY=
# path to playlist and user ids csv, usually starts with 'db/...'
# if you change this filename or the contents of the file, you must send a
# request to /admin/load-ids again
DB_IDS=
# if you change any of these filenames to a new empty/nonexistant file, you must
# send a request to /admin/load-ids again to initialize the file.
# path to playlists collection, usually starts with 'db/...'
DB_PLAYLISTS=
# path to users collection, usually starts with 'db/...'
DB_USERS=