-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathcortex_config.example.yaml
More file actions
46 lines (44 loc) · 2.43 KB
/
Copy pathcortex_config.example.yaml
File metadata and controls
46 lines (44 loc) · 2.43 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
38
39
40
41
42
43
44
45
46
# CORTEX internal test — configuration TEMPLATE.
#
# Copy this to cortex_config.yaml and fill it in. cortex_config.yaml is
# gitignored (it carries a live Dropbox token) — only this token-free
# template is tracked in git.
#
# Two independent ways to deliver each completed session's result CSVs to
# the PI. Configure either, both, or neither — results are always kept
# locally under results/sessions/<session_id>/ regardless.
# (1) synced_results_dir — a local folder that a Dropbox / Google Drive /
# iCloud desktop app syncs to the cloud. Leave empty to disable.
synced_results_dir: ""
# (2) dropbox — direct upload to Dropbox via the API (no desktop app
# needed on the test-taker's machine). See docs/CORTEX_DROPBOX_SETUP.md
# for the full setup walkthrough.
#
# PREFERRED: refresh-token mode. The bundle's short-lived access token
# is auto-renewed by the Dropbox SDK using a long-lived refresh token,
# so the bundle keeps working indefinitely. Generate the refresh
# token once with:
# .venv/bin/python scripts/cortex_dropbox_oauth.py
#
# For Confidential Dropbox apps (the default app type when you click
# "Create app"), app_secret is REQUIRED in addition to app_key +
# refresh_token — the SDK uses it for each token-refresh call. Leave
# app_secret empty only if your app is configured as Public (PKCE).
#
# LEGACY: access_token-only mode. Paste a short-lived token from the
# Dropbox app console; it expires in ~4 hours and the bundle then
# stops uploading. Retained only for one-off dev sessions.
#
# WARNING: whichever credentials you use ship inside the distributed
# zip. Always use an "App folder"-scoped app with only the
# files.content.write permission — the worst a leaked credential
# allows is writing files into that single app folder.
dropbox:
app_key: "" # PREFERRED: Dropbox app key (Settings tab)
app_secret: "" # PREFERRED for Confidential apps (the default)
refresh_token: "" # PREFERRED: from scripts/cortex_dropbox_oauth.py
access_token: "" # LEGACY: short-lived sl.u.AG… token (fallback)
folder: "/results/v1.2.0" # destination path inside the Dropbox app folder.
# v1.2.0 internal-test cohort writes here so it
# is logically isolated from v1.1.5 (/results/).
# Use /results/v2.0/ for the public-release cohort.