Check the File Locations page for the location that the configuration file should be placed. If you are creating the file using your systems File Explorer, you may need to enable hidden files/folders.
In the future, there will be a
hoard editcommand to automatically create and open the file.
The next step is determining what you are going to back up with Hoard. Common examples are configuration files for various programs and save files for PC games. Just like with Hoard's configuration file, these files are often found in hidden folders, so you may have to do some digging to find them.
For the sake of this guide, we will consider three different programs:
When adding configuration for a specific file or set of files, consider:
- What to name the hoard and, optionally, the pile or piles within it. See the examples linked above for ideas of how to structure hoards.
- What conditions must be true for a path to be used. These determine the environments, or
envsthat you will define.
- If there are multiple, mutually exclusive conditions that can be true at the same time (see
Vim and Neovim for an example). This determines if you need to add anything under
- Whether the programs use environment variables to determine where to place files, or if it is hardcoded. This will inform whether you use environment variables in the pile path or not.
- Whether there are files in a directory that you want to ignore when backing up.
When you think you have completed the configuration, double check by running
hoard validate. If there are any errors
with the configuration file, this command will tell you.
Once you have validated the configuration, run
hoard backup <hoard name>, where
<hoard name> is the name of the
hoard you just created. Alternatively, you can run
hoard backup to back up all configured hoards.
If you want to use Hoard to synchronize files between systems, you'll want to set up some sort of synchronization. Hoard aims to be agnostic to which method is used and only requires that the data files can be found in the expected location. This can be done by synchronizing that directory directly or by creating a symbolic link to another directory.
Possible sync solutions:
- A git repository on any hosting service
- File synchronization services like Nextcloud/ownCloud, Dropbox, Microsoft Onedrive, etc.
Whatever solution you choose, be aware of the possibility of synchronization conflicts. Hoard has no special logic to prevent synchronization-level conflicts, instead leaving that to the synchronization software itself.