Where `KEY` is the name of a *global* or *local* remote. **Path are not supported!**.
And `ARCHIVE` is an archive name defined in the `.borg` repository
And `ARCHIVE` is an archive name defined in the `.borg` repository or a branch/tag name of the git repository
Here are the steps that the push command execute:
...
...
@@ -909,6 +909,10 @@ Here are the steps that the push command execute:
4. Creates a tar archives and copy it in the local or a remote filesystem. If the tar archive should be exported to a remote file system, then the tar file is created locally (in .tmp folder at the project root) and then exported remotely using rsync.
::: {.callout-note}
In the case a git branch name is used in this command, only the archive of the commit pointed by this branch/tag will be pulled
:::
# Pull command
The pull commands allow to replace the content of your `.borg` archive into a remote folder.
...
...
@@ -920,7 +924,7 @@ gblk pull KEY ARCHIVES
```
Where `KEY` is the name of a *global* or *local* remote. **Path are not supported!**.
And `ARCHIVE` is an archive name defined in the `.borg` repository
And `ARCHIVE` is an archive name defined in the `.borg` repository or a branch/tag name of the git repository
Here are the steps that the pull command execute:
...
...
@@ -934,6 +938,10 @@ Here are the steps that the pull command execute:
You can you the `--all` flag to pull all archives in the remote directory instead of one particular archives.
:::
::: {.callout-note}
In the case a git branch name is used in this command, only the archive of the commit pointed by this branch/tag will be pulled