Add export TTL setting

Closes #1573 (closed)

I'm not sure if setting the TTL in minutes is a good idea, rather than seconds. We already have the worker_activity_timeout, license.ping_frequency and the 8 RQ timeouts in job_timeouts that all use seconds instead of minutes. I at least made the unit explicit in the code, but it will not be clear to sysadmins that this is the only setting out of 11 that uses minutes rather than seconds.

changed milestone to %Arkindex 1.5.1

requested review from @vrigal

assigned to @erouchet

I also think using seconds would be cleaner from an admin point of view.

Eventually we could use a more explicit message (e.g. "You have to wait XX minutes before starting a new export for this project."). humanize.time.precisedelta may help using a readable timedelta for the user.

resolved all threads

added 1 commit

• 7dd4a1de - Switch to seconds

Compare with previous version

approved this merge request

requested review from @babadie and removed review request for @vrigal

OK for seconds

added 8 commits

• 7dd4a1de...b1a79d84 - 6 commits from branch master
• e14f8192 - Add export TTL setting
• 9b9fdefa - Switch to seconds

Compare with previous version

enabled an automatic merge when the pipeline for 9b9fdefa succeeds

merged