rootCmd.PersistentFlags().StringVar(&flags.DOCKER_IMAGE,"docker-image","cupcakearmy/autorestic:"+internal.VERSION,"specify a custom docker image")
rootCmd.PersistentFlags().StringVar(&flags.DOCKER_IMAGE,"docker-image","cupcakearmy/autorestic:"+internal.VERSION,"specify a custom docker image")
rootCmd.PersistentFlags().StringVar(&flags.LOCKFILE_PATH,"lockfile-path","","specify a custom path for the lockfile (defaults to .autorestic.lock.yml next to the loaded autorestic config file)")
rootCmd.PersistentFlags().StringVar(&flags.LOCKFILE,"lockfile","","specify a custom path for the lockfile (defaults to .autorestic.lock.yml next to the loaded autorestic config file)")
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.
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.
@ -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:
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
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.
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.