docs

docs/markdown/migration/0.x_1.0.md

@@ -0,0 +1,26 @@
+# From `0.x` to `1.0`
+
+Most of the config file is remained compatible, however to clean up the backends custom environment variables were moved from the root object to an `env` object.
+
+```yaml
+# Before
+remote:
+    type: b2
+    path: bucket:path/to/backup
+    key: some random encryption key
+    B2_ACCOUNT_ID: id
+    B2_ACCOUNT_KEY: key
+
+# After
+remote:
+    type: b2
+    path: bucket:path/to/backup
+    key: some random encryption key
+    env:
+      B2_ACCOUNT_ID: id
+      B2_ACCOUNT_KEY: key
+```
+
+Other than the config file there is a new `-v, --verbose` flag which shows the output of native commands, which are now hidden by default.
+
+> :ToCPrevNext

docs/markdown/migration/1.4_1.5.md

@@ -0,0 +1,39 @@
+# Migration from `1.4` to `1.5`
+
+## Hooks
+
+Since `1.5` multiple sources for a location are possible.
+For this reason, while before hooks where executed in the folder of the source, now they are executed in the directory of the config `.autorestic.yaml`.
+
+You can overwrite this behavior with the new `dir` option in the hook section of the config.
+
+```yaml
+locations:
+  l1:
+    # ...
+    from: /foo/bar
+    hooks:
+      dir: /foo/bar
+      before: pwd
+```
+
+## Docker volumes
+
+The syntax with docker volumes has changed and needs to be adjusted.
+
+```yaml
+# Before
+locations:
+  foo:
+    from: volume:my-data
+```
+
+```yaml
+# After
+locations:
+  foo:
+    from: my-data
+    type: volume
+```
+
+> :ToCPrevNext