lifetime should be configurable
Bug #657033 reported by
Scott Moser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
awstrial |
Triaged
|
Medium
|
Dustin Kirkland |
Bug Description
Lifetime of the instance should be configurable.
In one (and only) one sense, it is.
settings.py:
LIFETIME = 60 * 55;
But we have other places in the code which are forcing 55 minutes.
a.) the countdown timer
b.) the at jobs scheduled
Probably some text in lots of other places.
Changed in awstrial: | |
status: | Confirmed → Triaged |
assignee: | nobody → Dustin Kirkland (kirkland) |
To post a comment you must log in.
@Scott, I should probably just look myself... but is it using LIFETIME, or literally hardcoded to 55m?