forked from qiita-spots/qiita
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathconfig_test.cfg
263 lines (211 loc) · 8.85 KB
/
config_test.cfg
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
# WARNING!!!! DO NOT MODIFY THIS FILE
# IF YOU NEED TO PROVIDE YOUR OWN CONFIGURATION, COPY THIS FILE TO A NEW
# LOCATION AND EDIT THE COPY
# -----------------------------------------------------------------------------
# Copyright (c) 2014--, The Qiita Development Team.
#
# Distributed under the terms of the BSD 3-clause License.
#
# The full license is in the file LICENSE, distributed with this software.
# -----------------------------------------------------------------------------
# ------------------------------ Main settings --------------------------------
[main]
# Change to FALSE in a production system
TEST_ENVIRONMENT = TRUE
# Absolute path to the directory where log files are saved. If not given, no
# log file will be created
LOG_DIR =
# Whether studies require admin approval to be made available
REQUIRE_APPROVAL = True
# Base URL: DO NOT ADD TRAILING SLASH
BASE_URL = https://localhost:8383
# Download path files
UPLOAD_DATA_DIR = /home/runner/work/qiita/qiita/qiita_db/support_files/test_data/uploads/
# Working directory path
WORKING_DIR = /home/runner/work/qiita/qiita/qiita_db/support_files/test_data/working_dir/
# Maximum upload size (in Gb)
MAX_UPLOAD_SIZE = 100
# Path to the base directory where the data files are going to be stored
BASE_DATA_DIR = /home/runner/work/qiita/qiita/qiita_db/support_files/test_data/
# Valid upload extension, comma separated. Empty for no uploads
VALID_UPLOAD_EXTENSION = fastq,fastq.gz,txt,tsv,sff,fna,qual
# The script used to start the qiita environment, if any
# used to spawn private CLI to a cluster
QIITA_ENV = source activate qiita
# Script used for launching private Qiita tasks
PRIVATE_LAUNCHER = qiita-private-launcher
# Script used for launching plugins
PLUGIN_LAUNCHER = qiita-plugin-launcher
# Plugins configuration directory
PLUGIN_DIR =
# Webserver certificate file paths
CERTIFICATE_FILE =
KEY_FILE =
# The value used to secure cookies used for user sessions. A suitable value can
# be generated with:
#
# python -c "from base64 import b64encode;\
# from uuid import uuid4;\
# print b64encode(uuid4().bytes + uuid4().bytes)"
COOKIE_SECRET = SECRET
# The value used to secure JWTs for delegated permission artifact download.
JWT_SECRET = SUPER_SECRET
# Address a user should write to when asking for help
HELP_EMAIL = [email protected]
# The email address, Qiita sends internal notifications to a sys admin
SYSADMIN_EMAIL = [email protected]
# ----------------------------- SMTP settings -----------------------------
[smtp]
# The hostname to connect to
# Google: smtp.google.com
HOST = localhost
# The port to connect to the database
# Google: 587
PORT = 25
# SSL needed (True or False)
# Google: True
SSL = False
# The user name to connect with
USER =
# The user password to connect with
PASSWORD =
# The email to have messages sent from
EMAIL = [email protected]
# ----------------------------- Redis settings --------------------------------
[redis]
HOST = localhost
PORT = 7777
PASSWORD =
# The redis database you will use, redis has a max of 16.
# Qiita should have its own database
DB = 13
# ----------------------------- Postgres settings -----------------------------
[postgres]
# The user name to connect to the database
USER = postgres
# The administrator user, which can be used to create/drop environments
ADMIN_USER = postgres
# The database to connect to
DATABASE = qiita_test
# The host where the database lives on
HOST = localhost
# The port to connect to the database
PORT = 5432
# The password to use to connect to the database
PASSWORD = postgres
# The postgres password for the admin_user
ADMIN_PASSWORD = postgres
# ----------------------------- Job Scheduler Settings -----------------------------
[job_scheduler]
# The email address of the submitter of jobs
JOB_SCHEDULER_JOB_OWNER = [email protected]
# The number of seconds to wait between successive calls
JOB_SCHEDULER__POLLING_VALUE = 15
# Hard upper-limit on concurrently running validator jobs
JOB_SCHEDULER_PROCESSING_QUEUE_COUNT = 2
# ----------------------------- EBI settings -----------------------------
[ebi]
# The user to use when submitting to EBI
EBI_SEQ_XFER_USER = Webin-41528
# Password for the above user
EBI_SEQ_XFER_PASS =
# URL of EBI's FASP site
EBI_SEQ_XFER_URL = webin.ebi.ac.uk
# URL of EBI's HTTPS dropbox
# live submission URL
#EBI_DROPBOX_URL = https://www.ebi.ac.uk/ena/submit/drop-box/submit/
# testing URL
EBI_DROPBOX_URL = https://www-test.ebi.ac.uk/ena/submit/drop-box/submit/
# The name of the sequencing center to use when doing EBI submissions
EBI_CENTER_NAME = qiita-test
# This string (with an underscore) will be prefixed to your EBI submission and
# study aliases
EBI_ORGANIZATION_PREFIX = example_organization
# ----------------------------- VAMPS settings -----------------------------
[vamps]
# general info to submit to vamps
USER = user
PASSWORD = password
URL = https://vamps.mbl.edu/mobe_workshop/getfile.php
# ----------------------------- Portal settings -----------------------------
[portal]
# Portal the site is working under
PORTAL = QIITA
# Portal subdirectory
PORTAL_DIR =
# Full path to portal styling config file
PORTAL_FP =
# The center latitude of the world map, shown on the Stats map.
# Defaults to 40.01027 (Boulder, CO, USA)
STATS_MAP_CENTER_LATITUDE =
# The center longitude of the world map, shown on the Stats map.
# Defaults to -105.24827 (Boulder, CO, USA)
STATS_MAP_CENTER_LONGITUDE =
# ----------------------------- iframes settings ---------------------------
[iframe]
# On May 2024, we removed QIIMP from the code base but we will leave this
# section in case we need to add access to another iframe in the future; note
# that the qiita-terms are also accessed via iframe but this is internal
# --------------------- External Identity Provider settings --------------------
# user authentication happens per default within Qiita, i.e. when a user logs in,
# the stored password hash and email address is compared against what a user
# just provided. You might however, use an external identity provider (IdP) to
# authenticate the user like
# google: https://developers.google.com/identity/protocols/oauth2 or
# github: https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/authorizing-oauth-apps or
# self hosted keycloak: https://www.keycloak.org/
# Thus, you don't have to deal with user verification, reset passwords, ...
# Authorization (i.e. if the authorized user is allowed to use Qiita or which
# user level he/she gets assigned is an independent process. You can even use
# multiple independent external identity providers!
# Qiita currently only support the "open ID connect" protocol with the implicit flow.
# Each identity provider comes as its own config section [oidc_foo] and needs
# to specify the following five fields:
#
# Typical identity provider manage multiple "realms" and specific "clients" per realm
# You need to contact your IdP and register Qiita as a new "client". The IdP will
# provide you with the correct values.
#
# The authorization protocol requires three steps to obtain user information:
# 1) you identify as the correct client and ask the IdP for a request code
# You have to forward the user to the login page of your IdP. To let the IdP
# know how to come back to Qiita, you need to provide a redirect URL
# 2) you exchange the code for a user token
# 3) you obtain information about the user for the obtaines user token
# Typically, each step is implemented as a separate URL endpoint
#
# To activate IdP: comment out the following config section
#[oidc_academicid]
#
## client ID for Qiita as registered at your Identity Provider of choice
#CLIENT_ID = gi-qiita-prod
#
## client secret to verify Qiita as the correct client. Not all IdPs require
## a client secret!
#CLIENT_SECRET = verySecretString
#
## redirect URL (end point in your Qiita instance), to which the IdP redirects
## after user types in his/her credentials. If you don't want to change code in
## qiita_pet/webserver.py the URL must follow the pattern:
## base_URL/auth/login_OIDC/foo where foo is the name of this config section
## without the oidc_ prefix!
#REDIRECT_ENDPOINT = /auth/login_OIDC/localkeycloak
#
## The URL of the well-known json document, specifying how API end points
## like 'authorize', 'token' or 'userinfo' are defined. See e.g.
## https://swagger.io/docs/specification/authentication/
## openid-connect-discovery/
#WELLKNOWN_URI = https://keycloak.sso.gwdg.de/.well-known/openid-configuration
#
## a speaking label for the Identity Provider. Section name is used if empty.
#LABEL = GWDG Academic Cloud
#
## The scope, i.e. fields about a user, which Qiita requests from the
## Identity Provider, e.g. "profile email eduperson_orcid".
## Will be automatically extended by the scope "openid", to enable the
## "authorize_code" OIDC flow.
#SCOPE = openid
#
##Optional. Name of a file in qiita_pet/static/img that shall be
##displayed for login through Service Provider, instead of a plain button
#LOGO = oidc_lifescienceAAI.png