docs: add information on run-schedule command

Author: creativeprojects

docs/content/configuration/logs/_index.md

@@ -137,6 +137,14 @@ profile:
 {{% /tab %}}
 {{< /tabs >}}
 
+## Priority on the log targets
+
+If specified in different places, here's the priority order for the log destination:
+1. `--log` flag on the command line
+2. `schedule-log` in the `profile` section
+3. `log` in the `global` section
+4. default to the console
+
 ## Send logs to a temporary file
 
 This can be done by using the [template]({{< ref "/configuration/templates" >}}) function `tempFile`.

docs/content/schedules/commands/index.md

@@ -1,15 +1,16 @@
 ---
 title: "Schedule Commands"
 weight: 20
+tags: ["v0.25.0"]
 ---
 
 
 resticprofile accepts these internal commands:
-- `schedule`
-- `unschedule`
-- `status`
+- **schedule**
+- **unschedule**
+- **status**
 
-All internal commands either operate on the profile selected by `--name`, on the profiles selected by a group, or on all profiles when the flag `--all` is passed.
+These resticprofile commands either operate on the profile selected by `--name`, on the profiles selected by a group, or on all profiles when the flag `--all` is passed on the command line.
 
 Examples:
 ```shell
@@ -39,3 +40,19 @@ Remove all the schedules defined on the selected profile or profiles.
 Print the status on all the installed schedules of the selected profile or profiles. 
 
 The display of the `status` command will be OS dependant. Please refer to the [examples]({{< ref "/schedules/examples" >}}) on which output you can expect from it.
+
+### run-schedule command
+
+This is the command that is used internally by the scheduler to tell resticprofile to execute in the context of a schedule. It means it will set the proper log output (`schedule-log`) and all other flags specific to the schedule.
+
+If you're scheduling resticprofile manually you can use this command. It will execute the profile using all the `schedule-*` parameters defined in the profile.
+
+This command is only taking one argument: name of the command to execute, followed by the profile name, both separated by a `@` sign.
+
+```shell
+resticprofile run-schedule backup@profile
+```
+
+{{% notice info %}}
+You cannot specify the profile name using the `--name` flag.
+{{% /notice %}}

docs/content/schedules/examples/index.md

@@ -356,5 +356,5 @@ If you backup your files to an external repository on a network, you should get
 If you prefer not being asked, you can add the `--no-start` flag like so:
 
 ```shell
-% resticprofile -v -c examples/private/azure.yaml -n self schedule --no-start
+resticprofile -v -c examples/private/azure.yaml -n self schedule --no-start
 ```