Expire maintainer invites and scheduled tasks for the database

[ewan-escience]

Expire maintainer invites and scheduled tasks for the database

Changes proposed in this pull request:

• Maintainer invites now expire 31 days after creation; this is implemented by an automatically generated column in the database
• Show the remaining validity of invites in days on the frontend
• Add documentation on how to schedule repeated tasks in the database

How to test:

• docker compose down --volumes && docker compose build --parallel && docker compose up --scale data-generation=1
• Sign in as admin, create maintainer invites for a software page, project and organisation
• Each invitation should show that it will expire in 31 days
• You can run the following snippet in the database to experiment with different expiration dates for software invites to check if the frontend behaves correctly:

  ALTER TABLE invite_maintainer_for_software DISABLE TRIGGER sanitise_update_invite_maintainer_for_software;
  UPDATE invite_maintainer_for_software SET created_at = CURRENT_TIMESTAMP - INTERVAL '31 days';
  ALTER TABLE invite_maintainer_for_software ENABLE TRIGGER sanitise_update_invite_maintainer_for_software;

• Check the updated docs on this
• Check the new section here on running repeated tasks
• Optional: you could run a cron job similar to the ones in the docs by adding the following line to your crontab, make sure to edit the paths

• • • • • docker-compose --file /home/ubuntu/docker-compose.yml exec -T database psql --dbname=rsd-db --username=rsd --command="SELECT COUNT(*) FROM software;" >> /home/ubuntu/cron.log 2>&1

Closes #260

PR Checklist:

• [ ] Increase version numbers in docker-compose.yml
• [x] Link to a GitHub issue
• [x] Update documentation
• [ ] Tests

[sonarcloud[bot]]

Quality Gate passed for 'rsd-database'

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarcloud[bot]]

Quality Gate passed for 'rsd-frontend'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[ewan-escience]

Would it be possible to install cron in the Postgres container so that we can add the scheduled task in the container?

We decided on investigating having a dedicated container for cron jobs.

About the 31 day, it is not allowed to use a subquery in a generated column, so we cannot use any env variables to change it. I'm fine with changing it to another value, like 14 days, but I don't think it's possible to make it configurable. You can of yourse change the column manually on your instance.