-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix MFA Bugs and Update .env Variables #539
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey. I think this is good. Just two comments about variable names and defaults and we should be able to deploy.
.env.example
Outdated
@@ -59,6 +59,9 @@ ELASTICSEARCH_VERIFY_CERTS=FALSE | |||
REDIS_HOST=<REDIS HOSTNAME> | |||
REDIS_PORT=<REDIS PORT> | |||
|
|||
# Celery | |||
CELERY_CLEAR_EXPIRED_SESSION_IDS=<CELERY_CLEAR_EXPIRED_SESSION_IDS> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we change this variable name to be something like CELERY_CLEAR_EXPIRED_SESSION_IDS_INTERVAL
that way we know exactly what it refers to?
app/celery_config.py
Outdated
|
||
CELERY_IMPORTS = ['app.jobs'] | ||
CELERY_TASK_RESULT_EXPIRES = 30 | ||
CELERY_TIMEZONE = 'EST' | ||
CELERY_CLEAR_EXPIRED_SESSION_IDS = os.environ.get('CELERY_CLEAR_EXPIRED_SESSION_IDS') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we have a default here (e.g. 0
)?
No description provided.