-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathconfig.yaml.example
103 lines (91 loc) · 3.17 KB
/
config.yaml.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
#
# DO NOT COMMIT THIS INTO SOURCE CONTORL
#
port: 3001
deployment_type: dev
log_file: dev.log
log_level: info
# Set to true if this is deployed behind a reverse proxy. This will almost
# always be true.
is_behind_reverse_proxy: true
# If you use a localhost URL here, have the port match the setting
# above. For non-dev deployments, it's preferable to use a publically
# available address with TLS.
public_url: http://localhost:3001
preferred_password_crypt_method: bcrypt_10
# Session cookie settings
#
# IMPORTANT: session_secret should be generated uniquely for the deployment.
# Try:
#
# $ dd if=/dev/urandom bs=1k count=1 | sha256sum
#
# And paste the hex string output as the session_secret value.
session_secret: xxxx
session_length_sec: 3600000
# Directory for storing photos. For development deployments, this can be
# test_data/photos/
photo_dir: test_data/photos/
# Size limit on photos. This is the transfer limit, and since the transfer
# is in base64, the encoded version is about 33% larger than the actual photo.
photo_size_limit: 10485760
# Wild Apricot API key. To generate a secret, you will need to setup a
# key in the Wild Apricot website. Someone with admin access on WA can
# follow the instructions at:
#
# https://gethelp.wildapricot.com/en/articles/180
#
wa_api_client: APIKEY
wa_api_secret: xxxxxxxx
wa_account_id: 227272
# Google OAuth2 client key credentials. Getting this is a bit of a process,
# so read these instructions carefully.
#
# Start by going to:
#
# https://console.developers.google.com
#
# Create a new project, then go to "Credentials". Create a new Oauth client ID.
# Select "Other" for "Application Type". Then hit "Download JSON" and save
# the file to the project directory as "google-credentials.json" (you can
# change this file name in "google_credentials_file" below).
#
# Next, you will need to get the URL for authorizing the key under your user.
# To do this, run:
#
# ts-node google_oauth.js
#
# This will output a URL, where you will need to authorize the scopes. After
# doing so, it will show a random string. The program will sit there until you
# put that token string in and hit <Enter>.
#
# If all goes will, this will give you the values for "google_access_token",
# "google_refresh_token", etc. Copy and paste its output of these fields,
# replacing the fields below
#
#
# - MAKE SURE THE google-credentials.json FILE NEVER GOES INTO SOURCE CONTROL -
#
# There is a .gitignore in place, so it should be OK.
#
google_credentials_file: google-credentials.json
google_client_token: xxxx
google_access_token: xxxx
google_token_type: Bearer
google_refresh_token: xxxx
google_expires_date: xxxx
# From name/email address for new member signup emails
email_new_member_signup_from_name: The Bodgery
email_new_member_signup_from_email: test@example.com
# Where to send the emails to the group about new member signup
email_group_new_member_signup_to_name: The Bodgery
email_group_new_member_signup_to_email: test@example.com
# Google Groups to add a new member
google_groups_signup_list:
- thebodgery@googlegroups.com
- madcitymakers@googlegroups.com
db_user: test
db_password: passwd
db_name: bodgery_members_yourname
db_host: localhost
db_port: 5432