docs: add changelog and remove tags

creativeprojects · creativeprojects · commit aab1a70d8db2 · 2025-04-04T21:21:25.000+01:00
diff --git a/docs/content/changelog.md b/docs/content/changelog.md
@@ -5,6 +5,33 @@ title: Release Notes
 weight: 8
 ---
 
+# v0.30.0 (2025-04-04)
+
+## 🌱 Spring release 🌸
+
+### ⚠️ Breaking change
+
+Until this release, the `user` scheduling permission was broken. With `systemd` or the default macOS scheduler, the permission functioned as `user_logged_on`, running the profile only when the user was logged in.
+
+This issue is now fixed for new schedules.
+
+To update existing schedules, run `unschedule` and then `schedule` again.
+
+For `systemd`, resticprofile requires root privileges (via sudo) to schedule with `user` permission, as it now uses a system unit running as the user.
+
+### Scheduler
+
+Scheduling has been significantly improved with the ability to read existing schedules. The `status` and `unschedule` commands now detect any resticprofile schedules from the selected configuration file, even if the profile is no longer present.
+
+Due to recent error reports, Windows Task Scheduler integration has been completely rewritten to use the `schtasks` CLI tool.
+
+### Other
+
+- Fixed issue with non-existent battery reported on recent Mac desktop hardware.  
+- Added support for Restic 0.18.  
+- Included pre-built binary for Windows on ARM64.  
+- Upload Resticprofile container to GitHub Container Registry.  
+
 # v0.29.1 (2025-02-06)
 
 ## ❄️  Small maintenance release ☃️ 
@@ -23,7 +50,7 @@ Not much going on in this maintenance release while I'm still working on a big r
 
 # v0.29.0 (2024-10-28)
 
-## 🧙🏻‍♀️  Halloween edition 🎃 
+## 🧙🏻‍♀️ Halloween edition 🎃 
 
 - Finally a long standing bug was fixed in this version: use proper `nice` and `ionice` values on `systemd` scheduled tasks.
 - Also the last chunk of work for the configuration `v2`: we can now schedule groups!
diff --git a/docs/content/configuration/copy.md b/docs/content/configuration/copy.md
@@ -1,6 +1,5 @@
 ---
 title: "Copy command"
-tags: ["v0.18.0", "v0.26.0"]
 weight: 17
 ---
 
diff --git a/docs/content/configuration/http_hooks.md b/docs/content/configuration/http_hooks.md
@@ -1,6 +1,5 @@
 ---
 title: "HTTP Hooks"
-tags: ["v0.18.0"]
 weight: 22
 ---
 
diff --git a/docs/content/configuration/include.md b/docs/content/configuration/include.md
@@ -1,6 +1,5 @@
 ---
 title: "Includes"
-tags: ["v0.18.0"]
 weight: 15
 ---
 
diff --git a/docs/content/configuration/jsonschema/index.md b/docs/content/configuration/jsonschema/index.md
@@ -1,6 +1,5 @@
 ---
 title: "JSON schema"
-tags: ["v0.21.0"]
 weight: 55
 ---
 
diff --git a/docs/content/configuration/logs.md b/docs/content/configuration/logs.md
@@ -1,6 +1,5 @@
 ---
 title: "Logs"
-tags: ["v0.21.0"]
 weight: 45
 ---
 
diff --git a/docs/content/configuration/priority.md b/docs/content/configuration/priority.md
@@ -1,6 +1,5 @@
 ---
 title: "Priority"
-tags: ["v0.27.0"]
 weight: 35
 ---
 
diff --git a/docs/content/configuration/sleep.md b/docs/content/configuration/sleep.md
@@ -1,6 +1,5 @@
 ---
 title: "Preventing system sleep"
-tags: ["v0.19.0"]
 weight: 40
 ---
 
diff --git a/docs/content/configuration/v2.md b/docs/content/configuration/v2.md
@@ -1,6 +1,5 @@
 ---
 title: "Configuration v2 proposal"
-tags: ["v1.0.0"]
 weight: 60
 ---
 
diff --git a/docs/content/schedules/_index.md b/docs/content/schedules/_index.md
@@ -92,3 +92,8 @@ profile:
 
 {{% /tab %}}
 {{< /tabs >}}
+
+
+## More information
+
+{{% children  %}}
diff --git a/docs/content/schedules/commands.md b/docs/content/schedules/commands.md
@@ -1,7 +1,6 @@
 ---
 title: "Schedule Commands"
 weight: 20
-tags: ["v0.25.0", "v0.29.0", "v0.30.0"]
 ---
 
 
diff --git a/docs/content/schedules/configuration.md b/docs/content/schedules/configuration.md
@@ -69,42 +69,42 @@ profile:
 {{< /tabs >}}
 
 
-### schedule-permission
+## schedule-permission
 
 `schedule-permission` accepts three parameters: `system`, `user`, or `user_logged_on`:
 
 * `system`: Access system or protected files. Run resticprofile with `sudo` on Unix and with elevated prompt on Windows. On Windows, resticprofile will automatically request elevated permissions if needed.
 
-* `user`: Run the backup using current user permissions. Suitable for saving documents or files within your profile. **This mode runs even when the user is not logged on**. It will ask for your user password on Windows.
+* `user`: Run the backup using current user permissions. Suitable for saving documents or files within your profile. **This mode runs even when the user is not logged on**. It will ask for your user password on Windows. It needs root permission (via sudo) when using `systemd`.
 
 * `user_logged_on`: **Not for crond** - Provides the same permissions as `user`, but runs only when the user is logged on. On Windows, it does not ask for your user password.
 
 * *empty*: resticprofile will guess based on how it was started (with sudo or as a normal user). The fallback is `system` on Windows and `user_logged_in` on other platforms.
 
-#### Changing schedule-permission
+### Changing schedule-permission
 
 To change the permission of a schedule, unschedule the profile first.
 
 Follow this order:
 
-- Unschedule the job first. Resticprofile does not track how your profile was installed, so you must remove the schedule first.
+- Unschedule the job first (before updating the permission in the configuration)
 - Change your permission (user to system, or system to user).
 - Schedule your updated profile.
 
 
-### schedule-lock-mode
+## schedule-lock-mode
 
 `schedule-lock-mode` accepts 3 values:
 - `default`: Waits for the duration set in `schedule-lock-wait` before failing a schedule. Acts like `fail` if `schedule-lock-wait` is "0" or not specified.
 - `fail`: Any lock failure immediately aborts the schedule.
 - `ignore`: Skips resticprofile locks. Restic locks are not skipped and can abort the schedule.
 
-### schedule-lock-wait
+## schedule-lock-wait
 
 Sets the wait time for a resticprofile and restic lock to become available. Used only when `schedule-lock-mode` is unset or `default`.
 
 
-### schedule-log
+## schedule-log
 
 `schedule-log` can be used in two ways:
 - Redirect all output from resticprofile **and restic** to a file. The parameter should point to a file (`/path/to/file`).
@@ -113,15 +113,15 @@ Sets the wait time for a resticprofile and restic lock to become available. Used
 If no server responds on the specified port, resticprofile will send the logs to the default output instead.
 
 
-### schedule-priority
+## schedule-priority
 
 `schedule-priority` accepts two values:
 - `background`: The process runs unnoticed while you work.
 - `standard`: The process gets the same priority as other processes (won't run faster if the machine is idle).
 
 `schedule-priority` is not available for crond.
 
-### schedule
+## schedule
 
 The `schedule` parameter accepts various forms of input from the [systemd calendar event](https://www.freedesktop.org/software/systemd/man/systemd.time.html#Calendar%20Events) type. This format is the same used to schedule on macOS and Windows.
 
@@ -174,11 +174,11 @@ Wed..Sat,Tue 12-10-15 1:2:3 → Tue..Sat 2012-10-15 01:02:03
 
 The `schedule` can be a string or an array of strings (to allow for multiple schedules).
 
-### schedule-ignore-on-battery
+## schedule-ignore-on-battery
 
 If set to `true`, the schedule won't start if the system is running on battery (even if the charge is at 100%).
 
-### schedule-ignore-on-battery-less-than
+## schedule-ignore-on-battery-less-than
 
 If set to a number, the schedule won't start if the system is running on battery and the charge is less than or equal to the specified number.
 
@@ -229,8 +229,8 @@ self:
   backup:
     source: "."
     schedule:
-    - "Mon..Fri *:00,15,30,45" # every 15 minutes on weekdays
-    - "Sat,Sun 0,12:00"        # twice a day on week-ends
+      - "Mon..Fri *:00,15,30,45" # every 15 minutes on weekdays
+      - "Sat,Sun 0,12:00"        # twice a day on week-ends
     schedule-permission: user
     schedule-lock-wait: 10m
   prune:
diff --git a/docs/content/schedules/examples.md b/docs/content/schedules/examples.md
@@ -337,9 +337,12 @@ Normalized form: *-*-* 22:22:00
 
 ```
 
-In some cases, macOS may request permission to access the network, an external volume (like a USB drive), or a protected directory. A message will appear while the backup runs in the background.
+{{% notice info %}}
 
-To respond immediately, start the task now:
+In some cases, macOS may request permission to access the network, an external volume (like a USB drive), or a protected directory. A message window will appear while the backup runs in the background.
+{{% /notice %}}
+
+You may want to start the task now so you can grant special permissions:
 
 1. Retrieve the task name using the status command:
 
diff --git a/docs/content/schedules/launchd.md b/docs/content/schedules/launchd.md
@@ -9,7 +9,7 @@ weight: 110
 
 A user agent is generated when you set `schedule-permission` to `user` or `user_logged_on`. It consists of a `plist` file in `~/Library/LaunchAgents`.
 
-If you include specific files in your backup, like contacts or calendar, you need to grant more permissions to resticprofile and restic (a popup window will ask for permission).
+If you include specific files in your backup (like contacts or calendar) or if you're connecting to an external restic repository, you may need to grant more permissions to resticprofile and restic (a popup window will ask for permission).
 
 You can wait for the profile to start or start it manually. To start a backup profile called `remote` manually, use:
 
diff --git a/docs/content/schedules/non-root-schedule-in-container.md b/docs/content/schedules/non-root-schedule-in-container.md
@@ -1,7 +1,6 @@
 ---
 title: "User schedule in container"
 weight: 200
-tags: ["v0.27.0"]
 ---
 
 
diff --git a/docs/content/schedules/systemd.md b/docs/content/schedules/systemd.md
@@ -1,7 +1,6 @@
 ---
 title: "Systemd"
 weight: 105
-tags: ["v0.25.0", "v0.29.0"]
 ---
 
 
diff --git a/docs/content/status/prometheus.md b/docs/content/status/prometheus.md
@@ -124,7 +124,7 @@ resticprofile_backup_status{profile="prom"} 2
 resticprofile_backup_time_seconds{profile="prom"} 1.707863748e+09
 # HELP resticprofile_build_info resticprofile build information.
 # TYPE resticprofile_build_info gauge
-resticprofile_build_info{goversion="go1.22.0",profile="prom",version="0.26.0-dev"} 1
+resticprofile_build_info{goversion="go1.22.0",profile="prom",version="0.26.0"} 1
 
 ```
 
diff --git a/docs/content/usage/_index.md b/docs/content/usage/_index.md
@@ -3,7 +3,6 @@ archetype: "chapter"
 pre: "<b>3. </b>"
 title: "Using resticprofile"
 weight: 3
-tags: ["v0.17.0"]
 ---
 
 Here are a few examples how to run resticprofile (using the main example configuration file)
@@ -34,7 +33,7 @@ Backup root & src profiles (using _full-backup_ group shown earlier)
 ```shell
 resticprofile --name "full-backup" backup
 ```
-or using the syntax introduced in v0.17.0:
+or using the alternative syntax:
 
 ```shell
 resticprofile full-backup.backup
@@ -45,7 +44,7 @@ Assuming the _stdin_ profile from the configuration file shown before, the comma
 ```shell
 mysqldump --all-databases --order-by-primary | resticprofile --name stdin backup
 ```
-or using the syntax introduced in v0.17.0:
+or using the alternative syntax:
 
 ```shell
 mysqldump --all-databases --order-by-primary | resticprofile stdin.backup
diff --git a/docs/hugo.toml b/docs/hugo.toml
@@ -40,10 +40,10 @@ publishdir = "../public/"
   main = false
   type = 'menu'
 
-[[menu.shortcuts]]
-  name = "<i class='fas fa-tags'></i> Tags"
-  url = "/tags"
-  weight = 10
+# [[menu.shortcuts]]
+#   name = "<i class='fas fa-tags'></i> Tags"
+#   url = "/tags"
+#   weight = 10
 
 [[menu.shortcuts]]
   name = "<i class='fab fa-fw fa-github'></i> GitHub repo"
