diff options
| author |  Alexandre Alapetite <alexandre@alapetite.fr>
| 2022-01-08 21:58:55 +0100 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2022-01-08 21:58:55 +0100 |
| commit | 1acd3ab09be1b65bfd6122ee351490c3b5527bb8 (patch) | |
| tree | f11de558e7a09522a45d1c155d9707ecda6bf1eb /docs/en/admins/08_FeedUpdates.md | |
| parent | 916df412f5b6f7fb9bcfb705a3c8c23e35304410 (diff) | |
Use typographic quotes (#4133)
* Use typographic quotes
* A few fixes
* Fix
* Fix not saved
* Implement feedback
* Detail
* Revert spoken English fixes
Left for a future dedicated discussion
* More reverts
* Final reverts
* Final minor
Diffstat (limited to 'docs/en/admins/08_FeedUpdates.md')
| -rw-r--r-- | docs/en/admins/08_FeedUpdates.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/en/admins/08_FeedUpdates.md b/docs/en/admins/08_FeedUpdates.md index e1a02af31..2072188bd 100644 --- a/docs/en/admins/08_FeedUpdates.md +++ b/docs/en/admins/08_FeedUpdates.md @@ -2,17 +2,17 @@ FreshRSS is updated by the `./app/actualize_script.php` script. Knowing this, we can periodically trigger it to ensure up-to-date feeds. -**Note:** the update script won't update any particular feed more often than once every twenty minutes, so it doesn't make sense to trigger it much more frequently than that. +**Note:** the update script won’t update any particular feed more often than once every twenty minutes, so it doesn’t make sense to trigger it much more frequently than that. -**Note:** the following examples assume that FreshRSS is installed to `/usr/share/FreshRSS`. You'll need to modify the FreshRSS path to reflect your own system. +**Note:** the following examples assume that FreshRSS is installed to `/usr/share/FreshRSS`. You’ll need to modify the FreshRSS path to reflect your own system. **Note:** If you cannot configure a local Cronjob, [see an alternative using online cron](../users/03_Main_view.md#online-cron). ## Cron as a trigger -You'll need to check the Cron documentation for your specific distribution ([Debian/Ubuntu](https://help.ubuntu.com/community/CronHowto), [Red Hat/Fedora/CentOS](https://fedoraproject.org/wiki/Administration_Guide_Draft/Cron), [Slackware](https://docs.slackware.com/fr:slackbook:process_control?#cron), [Gentoo](https://wiki.gentoo.org/wiki/Cron), [Arch Linux](https://wiki.archlinux.org/index.php/Cron) ...) to make sure you set the Cron job correctly. +You’ll need to check the Cron documentation for your specific distribution ([Debian/Ubuntu](https://help.ubuntu.com/community/CronHowto), [Red Hat/Fedora/CentOS](https://fedoraproject.org/wiki/Administration_Guide_Draft/Cron), [Slackware](https://docs.slackware.com/fr:slackbook:process_control?#cron), [Gentoo](https://wiki.gentoo.org/wiki/Cron), [Arch Linux](https://wiki.archlinux.org/index.php/Cron) …) to make sure you set the Cron job correctly. -It's advisable that you run the Cron job as your Web server user (often `www-data`). +It’s advisable that you run the Cron job as your Web server user (often `www-data`). ### Example on Debian/Ubuntu @@ -25,7 +25,7 @@ Edit `/etc/crontab` and append the following line: ## Systemd as a trigger -Some systems can't use a Cron job, but they can use systemd. It's easy to configure it to mimic Cron's features. +Some systems can’t use a Cron job, but they can use systemd. It’s easy to configure it to mimic Cron’s features. First you need to add a `freshrss.timer` file in `/etc/systemd/system/` with the following content: |