chore(lockfile) change flag to --lockfile

This is more consistent with the `lockfile` config option
This commit is contained in:
Boris Bera
2024-12-01 14:53:25 -05:00
parent de0862a3dd
commit 59b2393127
6 changed files with 17 additions and 17 deletions

View File

@@ -35,10 +35,10 @@ With `--restic-bin` you can specify to run a specific restic binary. This can be
autorestic --restic-bin /some/path/to/my/custom/restic/binary
```
## `--lockfile-path`
## `--lockfile`
Specify the path for the [lockfile](../lockfile.md) used by `autorestic`. If omitted, this will default to `.autorestic.lock.yml` next to the loaded config file.
```bash
autorestic --lockfile-path /path/to/my/.autorestic.lock.yml
autorestic --lockfile /path/to/my/.autorestic.lock.yml
```

View File

@@ -8,7 +8,7 @@ By default, the lockfile is stored next to your [configuration file](./config.md
The path to the lockfile can be customized if need be. This can be done is a few ways:
1. Using the `--lockfile-path ...` command line flag
1. Using the `--lockfile ...` command line flag
1. Setting `lockfile: ...` in the configuration file
Note that `autorestic` will check for a customized lockfile path in the order listed above. This means that if you specify a lockfile path in multiple places, the method that's higher in the list will win.