blob: a7d1a95148e3fa4c14119a9211b214c626f8c79f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
|
Cronjobs
========
There are some maintenance jobs that should be done at regular intervals to
keep the instance running smoothly:
* Old, abandoned uploads should be deleted from the database to free up the
space of the temporary GPX files.
* Tracks that are not present in the cache should have their cache entry
populated by pre-calculating their length/uphill/downhill/… values. This
makes accessing those values faster when a user requests the track's details.
Fietsboek comes with a script to deal with those jobs: ``fietscron``. You can
run it like this::
fietscron -c path_to_config.ini
You can use any mechanism you like to run this command at pre-defined intervals
(e.g. once an hour). You can find information about this in various sources:
* https://wiki.archlinux.org/title/Systemd/Timers
* https://wiki.archlinux.org/title/Cron
* https://wiki.gentoo.org/wiki/Cron
For example, the classic *cron*-way to run ``fietscron`` once per hour would be
to add the following to your *crontab* (using ``crontab -e``)::
0 * * * * /path/to/venv/bin/fietscron -c /path/to/settings.ini
|
