-
Notifications
You must be signed in to change notification settings - Fork 18
/
Copy pathdefines.yaml.example
94 lines (78 loc) · 3.41 KB
/
defines.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
################## Airscore settings ##################
# on/off ability to see and reuse waypoint and airspace files between comps.
# recommended for small user base. i.e. national associations
waypoint/airspace_file_library: off
# store pilots in airscore for use in comps.
# The alternative is to import a list of competitors for each comp.
# Using a internal pilot DB is recommended for clubs and national organisations.
# note that even if using an internal pilot DB you can still import external pilots for a comp
# (guest pilots, particular events etc.)
use_internal_pilot_DB: no
# if use_internal_pilot_DB is yes the below settings are relevant
internal_pilot_DB:
# if Airscore store and modify pilots.
# The reason you may not want to do this is if you connect the pilot DB to an external source.
write_to_internal_pilot_DB: no
# Each comp can be setup that a pilot (given a login) can self register for an event.
# This is the default value on creating a new competition
self_registration_default: on
# Each event can be setup that a pilot does not need to register, uploading a relevant track will do it.
# Default in no and at the moment code is not complete to permit this yet.
allow_open_event: no
# use internal table for admins and scorekeepers
use_internal_admin_DB: yes
# if use_internal_admin_DB is yes the below settings are relevant
internal_admin_DB:
# allows anyone to create a scorekeeper account
allow_self_registration: yes
# if use_internal_admin_DB is no the below settings are relevant
external_admin_DB:
auth_url: https://legapiloti.it/wp-json/wp/v2/users/me
auth_type: rest # rest, ajax, ...
competition_season:
#start_year: previous or current offset -1 or 0
#if season starts during previous year e.g. 2019 season starts 1st november 2018 then -1
start_year: -1
start_month: 11
start_day: 1
end_month: 10
end_day: 31
sanctions:
- none
- League
- PWC
- FAI 2
- FAI 1
igc_sources:
xcontest: off
flymaster: on
g_record_validation_server: http://vali.fai-civl.org/api/vali/json
flymaster_live_server: https://wlb.flymaster.net/getLiveData.php?
# Telegram Bot Service.
# switch telegram bot update feature on or off
telegram: off
# Ladders / League Ranking System - summing up several comps into a leaderboard.
# switch ladder classifications on or off
ladders: off
# folder structure, this is not intended for users to alter.
dir:
bin: /app/airscore/core/
tracks: /app/airscore/data/tracks/
waypoint: /app/airscore/data/waypoints/
json: /app/airscore/data/json/
log: /app/airscore/data/log/
image: /app/airscore/data/images/
map: /app/airscore/data/map-objects/
result: /app/airscore/data/results/
airspace: /app/airscore/data/airspace/openair/
airspace_map: /app/airscore/data/map-objects/airspace/
airspace_check: /app/airscore/data/airspace/check_file/
livetracking: /app/airscore/data/livetracking/
example_file: /app/airscore/example_files/
igc_parsing_config: /app/airscore/igc_parsing_config/
temp_files: /app/airscore/data/temp/
##########################################################################################################################
# FAI Sphere. Note that the use of FAI Sphere is obsolete with both PG and HG recommended to use the WGS84 ellipsoid by CIVL.
# this setting is only intended for testing Airscore against old competitions that were run with the FAI Sphere.
# Set to off to use WGS84, on for FAI Sphere.
FAI_sphere: off