aboutsummaryrefslogtreecommitdiff
path: root/docs/en/users/03_Main_view.md
diff options
context:
space:
mode:
authorGravatar Frans de Jonge <fransdejonge@gmail.com> 2018-11-18 21:08:41 +0100
committerGravatar Alexandre Alapetite <alexandre@alapetite.fr> 2018-11-18 21:08:41 +0100
commite2cb8b929bba51cbfa8c28200881899c451ec7d2 (patch)
tree58dad135853ff653f17361ba358fbf26b16c8a4b /docs/en/users/03_Main_view.md
parentebb9ee0873333c111546412ad08bf5207529f24a (diff)
[docs] Add note about specific user for webcron (#2142)
* [docs] Add note about specific user for webcron Cf. https://github.com/FreshRSS/FreshRSS/issues/613#issuecomment-353585547 * Small changes * Use one of the RFC addresses for examples
Diffstat (limited to 'docs/en/users/03_Main_view.md')
-rw-r--r--docs/en/users/03_Main_view.md13
1 files changed, 9 insertions, 4 deletions
diff --git a/docs/en/users/03_Main_view.md b/docs/en/users/03_Main_view.md
index 57eab192d..53d7131b6 100644
--- a/docs/en/users/03_Main_view.md
+++ b/docs/en/users/03_Main_view.md
@@ -35,14 +35,14 @@ Here is an example to trigger article update every hour.
If you do not have access to the installation server scheduled task, you can still automate the update process.
-To do so, you need to create a scheduled task, which need to call a specific URL: https://your.server.net/FreshRSS/p/i/?c=feed&a=actualize (it could be different depending on your installation). Depending on your application authentication method, you need to adapt the scheduled task.
+To do so, you need to create a scheduled task, which need to call a specific URL: https://freshrss.example.net/i/?c=feed&a=actualize (it could be different depending on your installation). Depending on your application authentication method, you need to adapt the scheduled task.
#### No authentication
This is the most straightforward since you have a public instance; there is nothing special to configure:
```cron
-0 * * * * curl 'https://your.server.net/FreshRSS/p/i/?c=feed&a=actualize'
+0 * * * * curl 'https://freshrss.example.net/i/?c=feed&a=actualize'
```
### Form authentication
@@ -60,16 +60,21 @@ You can also configure an authentication token to grant a special right on the s
The scheduled task syntax to use will be the following:
```cron
-0 * * * * curl 'https://your.server.net/FreshRSS/p/i/?c=feed&a=actualize&token=my-token'
+0 * * * * curl 'https://freshrss.example.net/i/?c=feed&a=actualize&token=my-token'
```
+You can also target a different user by adding their username to the query string, with `&user=insert-username`:
+
+```cron
+0 * * * * curl 'https://freshrss.example.net/i/?c=feed&a=actualize&user=someone&token=my-token'
+```
### HTTP authentication
In that case, the syntax in the two previous section are unusable. It means that you need to provide your credentials to the scheduled task. **Note that this method is highly discouraged since it means that your credentials will be in plain sight!**
```cron
-0 * * * * curl -u alice:password123 'https://your.server.net/FreshRSS/p/i/?c=feed&a=actualize'
+0 * * * * curl -u alice:password123 'https://freshrss.example.net/i/?c=feed&a=actualize'
```
## Manual update