Skip to content
Snippets Groups Projects
Verified Commit 883fdbee authored by Andreas Ellewsen's avatar Andreas Ellewsen
Browse files

Move djangoq settings to base settings

Done to make djangoq settings accessible in production.
The sync setting is changed to the default False value since the run
order of the tasks is not relevant for our use case.
Mail sending functions have gotten a sync argument to force the tasks to
complete before checking their consequences in tests.
parent 273bb4bf
No related branches found
No related tags found
1 merge request!222Move djangoq settings to base settings
Pipeline #107918 passed
......@@ -304,3 +304,15 @@ ORGREG_EXTRA_IDS = []
# Acronyms to be imported as identifiers from orgreg. List of acronym values, supported ones are: nob, nno, eng
# Example list: ["nob"]
ORGREG_ACRONYMS = []
# Settings related to Django-q used for scheduling tasks in the future.
# We use it to queue creation of Notification objects related to roles when start/end dates are in the future
Q_CLUSTER = {
"name": "greg",
"workers": 4,
"timeout": 90,
"retry": 120,
"queue_limit": 50,
"bulk": 10,
"orm": "default",
}
......@@ -30,16 +30,12 @@ CEREBRUM_CLIENT = {
}
CEREBRUM_HIERARCHICAL_ACCESS = True
Q_CLUSTER = {
"name": "greg",
"workers": 4,
"timeout": 90,
"retry": 120,
"queue_limit": 50,
"bulk": 10,
"orm": "default",
"sync": True,
}
Q_CLUSTER.update(
{
"sync": True,
}
)
AUTHENTICATION_BACKENDS = [
"gregui.authentication.auth_backends.DevBackend", # Fake dev backend
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment