-
Notifications
You must be signed in to change notification settings - Fork 2
/
.env.example
35 lines (29 loc) · 1.45 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
# Since the ".env" file is gitignored, you can use the ".env.example" file to
# build a new ".env" file when you clone the repo. Keep this file up-to-date
# when you add new variables to `.env`.
# This file will be committed to version control, so make sure not to have any
# secrets in it. If you are cloning this repo, create a copy of this file named
# ".env" and populate it with your secrets.
# When adding additional environment variables, the schema in "/src/env.cjs"
# should be updated accordingly.
# Next Auth
# You can generate a new secret on the command line with:
# openssl rand -base64 32
# https://next-auth.js.org/configuration/options#secret
NEXTAUTH_SECRET="supersecret"
NEXTAUTH_URL="http://localhost:3000"
NEXTAUTH_URL_INTERNAL="http://localhost:3000"
DATABASE_URL="postgresql://postgres:example@localhost:5432"
APP_URL="http://localhost:3000"
NEXT_PUBLIC_WS_URL="ws://localhost:3001"
NEXT_PUBLIC_MOCK_AUTH="false"
PLAYERS_PER_MATCH="3"
ALEO_NETWORK_URL="http://localhost:3030"
# The following is just a key used for testing and does not represent a public aleo account.
# When developing, make sure it's the same private key used to run the local devnet
ALEO_PRIVATE_KEY="APrivateKey1zkp8CZNn3yeCseEtxuVPbDCwSyhGW6yZKUYKfgXmcpoGPWH"
LEADERBOARD_PROGRAM_NAME="leaderboard.aleo"
AWS_ACCESS_KEY="<your_access_key>"
AWS_SECRET="<your_secret>"
AWS_INFERENCE_URL="https://3dhomhunle.execute-api.us-east-1.amazonaws.com/default/converse"
LAMBDA_TOKEN="<your_token>"