-
Notifications
You must be signed in to change notification settings - Fork 344
/
settings.yml
288 lines (270 loc) · 7.93 KB
/
settings.yml
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
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
# Note that changes to this file require a server restart to take effect.
############################
#
# ADMIN INTERFACE SETTINGS
#
############################
#
# These will be the values that admin interface users will choose from when
# updating a Service's accepted methods of payment. Make sure to update
# these values to match the ones in your data, as well as any additional
# ones you want to use that might not already be in your data.
#
# The list below should remain alphabetical, and should encompass all possible
# payment methods across all services.
accepted_payments:
- 'Cash'
- 'Check'
- 'Credit Card'
- 'EBT Card'
- 'Medicare'
# The email address that admin interface users should send questions/issues to.
# This link appears when an admin views their locations and organizations.
# See app/views/admin/locations/index.html.haml and
# app/views/admin/organizations/index.html.haml.
#
# Please make sure to change this to your own email address.
admin_support_email: ohanapi@codeforamerica.org
# These will be the values that admin interface users will choose from when
# updating an Organization's or Service's funding sources. Make sure to update
# these values to match the ones in your data, as well as any additional
# ones you want to use that might not already be in your data.
#
# The list below should remain in alphabetical order.
funding_sources:
- 'City'
- 'County'
- 'Donations'
- 'Dues'
- 'Endowments'
- 'Federal'
- 'Fees'
- 'Fundraising'
- 'Grants'
- 'Sales'
- 'Sponsorships'
- 'State'
- 'Taxes'
- 'United Way'
# An array of email domain names used by the admin interface to determine which
# users get to access which locations. For convenience, the API allows a client
# to retrieve locations that match a particular domain name. This means that
# when someone signs in to the admin interface with an organization email
# address, like "moncef@codeforamerica.org", then they will have access to all
# locations that match "codeforamerica.org". This works for these types of
# organization domain names, but if we allowed the same lookup for people with
# generic email addresses that end in "@gmail.com" for example, then they would
# be able to access all locations with "gmail.com" in the "email" field.
# To prevent that, the API compares the domain name with the list of generic
# domains that you define below, and if it finds it, then it looks for an exact
# match of the full email address.
#
# Depending on the email addresses present in your data, you might need to add
# domains to the list below. For example, in San Mateo County, many employees
# have a generic "@smcgov.org" email, even though they work in different
# departments, and should only be able to access their specific locations.
#
# This setting is used in 'app/models/concerns/search.rb'.
generic_domains:
- gmail.com
- aol.com
- sbcglobal.net
- hotmail.com
- yahoo.com
- comcast.net
# These will be the values that admin interface users will choose from when
# updating a Location's or a Service's languages. Make sure to update
# these values to match the ones in your data, as well as any additional
# ones you want to use that might not already be in your data.
#
# The list below should remain in alphabetical order.
languages:
- 'American Sign Language'
- 'Amharic'
- 'Arabic'
- 'Aramaic'
- 'Armenian'
- 'Assyrian'
- 'Bengali'
- 'Bosnian'
- 'Burmese'
- 'Cambodian'
- 'Cantonese'
- 'Cebuano'
- 'Chinese'
- 'Creole'
- 'Croatian'
- 'Czech'
- 'Danish'
- 'Dutch'
- 'Fijian'
- 'Filipino'
- 'Finnish'
- 'French'
- 'Fulani'
- 'Gaelic'
- 'German'
- 'Greek'
- 'Gujarati'
- 'Hausa'
- 'Hebrew'
- 'Hiligaynon'
- 'Hindi'
- 'Hmong'
- 'Hungarian'
- 'Igbo'
- 'Ilocano'
- 'Indonesian'
- 'Italian'
- 'Japanese'
- 'Kapampangan'
- 'Khmer'
- 'Kinyarwanda'
- 'Korean'
- 'Krio'
- 'Lao'
- 'Latvian'
- 'Maltese'
- 'Mandarin'
- 'Marathi'
- 'Mende'
- 'Mien'
- 'Mongolian'
- 'Ningbo'
- 'Norwegian'
- 'Oromo'
- 'Pangasinan'
- 'Persian'
- 'Polish'
- 'Portuguese'
- 'Punjabi'
- 'Romanian'
- 'Russian'
- 'Samoan'
- 'Serbo-Croatian'
- 'Shanghainese'
- 'Sindhi'
- 'Sinhalese'
- 'Somali'
- 'Spanish'
- 'Swahili'
- 'Swedish'
- 'Tagalog'
- 'Taiwanese'
- 'Tamil'
- 'Telugu'
- 'Temne'
- 'Thai'
- 'Tibetan'
- 'Tigrinya'
- 'Tongan'
- 'Ukrainian'
- 'Urdu'
- 'Vietnamese'
- 'Yiddish'
- 'Yoruba'
# These will be the values that admin interface users will choose from when
# updating a Service's required documents. Make sure to update
# these values to match the ones in your data, as well as any additional
# ones you want to use that might not already be in your data.
#
# The list below should remain in alphabetical order.
required_documents:
- 'Bank statements (last 3 months)'
- 'Government-issued picture identification'
# If your data contains a service_areas field that identifies which particular
# areas of a city or county are eligible for the services provided by an
# organization, and if you want to make sure that the service areas are always
# spelled the same way, then enter them below, one per line preceded by a dash
# and a space, just like the generic_domains above. Make sure to preserve the
# 2-space indentation. For example:
# valid_service_areas:
# - 'Alameda County'
# - 'Oakland'
#
# These will be the values that admin interface users will choose from when
# updating a Service's service areas. Make sure to update
# these values to match the ones in your data, as well as any additional
# ones you want to use that might not already be in your data.
#
# The list below should remain in alphabetical order.
valid_service_areas:
- 'Alameda County'
- 'Belmont'
- 'Burlingame'
- 'Colma'
- 'Daly City'
- 'East Palo Alto'
- 'San Mateo County'
- 'South San Francisco'
############################
#
# DATE SETTINGS
#
############################
#
# The date format to use for the Organization `date_incorporated` field,
# and for the Holiday Schedule `start_date` and `end_date` fields.
# The default format is the US-style month/day/year. To use the day/month
# style, change the value below to '%d/%m/'.
date_format: '%m/%d/'
############################
#
# EMAIL DELIVERY SETTINGS
#
############################
#
# The email address that confirmation emails are sent from after user signup,
# for the Developer and Admin portals.
# Please make sure to change this to your own email address.
confirmation_email: ohanapi@codeforamerica.org
###############################
#
# GEOGRAPHICAL BOUNDS SETTINGS
#
###############################
#
# Google provides a "bounds" option to restrict the address search to
# a particular area. This allows Google to disambiguate between two
# cities with the same name. For example, there is a city in San Mateo
# County called 'Brisbane'. There also happens to be a 'Brisbane' in
# Australia. If you didn't restrict the search to within San Mateo County,
# and you searched for locations near 'Brisbane', Google would look in
# Australia by default, and you wouldn't get any results.
#
# The bounds are defined by the SW and NE geo coordinates of your search area.
# It should be an array of two arrays. The first array should represent the
# SW coordinates, and the second the NE coordinates. Within each inner array,
# the coordinates should be Floats in [latitude, longitude] order. For example:
# bounds: [[37.1074, -122.521], [37.7084, -122.085]]
#
# The app is set to search within the continental US by default.
# Make sure to change the coordinates to match your preferred search area.
#
# This setting is used in 'app/models/concerns/search.rb'.
bounds: [[25.7084, -124.085], [48.9084, -67.085]]
###########################################
#
# SETTINGS FOR TESTS. PLEASE DO NOT MODIFY.
#
###########################################
test:
accepted_payments:
- 'Cash'
- 'Check'
bounds: [[37.1074, -122.521], [37.7084, -122.085]]
confirmation_email: registration@ohanapi.org
funding_sources:
- 'State'
- 'County'
languages:
- 'Arabic'
- 'French'
- 'Spanish'
required_documents:
- 'Bank Statement'
- 'Picture ID'
valid_service_areas:
- 'Atherton'
- 'Belmont'
date_format: '%m/%d/'