Added some notes about Celery settings vars #561 #562
Conversation
| ``` | ||
|
|
||
| ## Celery settings |
There was a problem hiding this comment.
Why do we have these in troubleshooting section? Should not we at least mention few most common issues?
Also there is flask cmd to test if celery is working, worth mentioning.
There was a problem hiding this comment.
@varmar05 Do you prefer a specific section for this or under 'Install' section?
There was a problem hiding this comment.
basic settings we can have in 'install' section or with other env variables - ideally our default should be reasonable so users do not need to change anything (unless they know what they are doing)
but because of common issues with celery we should have some trouble shooting section as well - at least to verify that celery is running and accepting tasks
| ``` | ||
|
|
||
| ## Celery settings |
There was a problem hiding this comment.
Add some troubleshooring context to this
|
I would mention here mainly that BROKER URL needs to be correct and celery-beat, celery-worker containers should be up and running. |
| | `PROJECT_ACCESS_REQUEST` | integer | `604800` | Lifetime of active project access request in seconds. | | ||
| | `TEMP_EXPIRATION` | integer | `7` | Time in days after files in a temporary folder are permanently deleted. | | ||
| | Variable name | Type | Default | Description | | ||
| |------------------------------|----------|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| |
There was a problem hiding this comment.
hm? too much ---- or is it ok?
|
@alex-cit could you review spelling here, thanks :) |
To be reviewed...