Use a placeholder host in the install instructions
ci/woodpecker/pr/test Pipeline was successful
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/lint Pipeline was successful

The install snippets named one specific artifact repository by hostname.

- fetch the release zip from a placeholder host under the same tag-archive
  path shape
This commit is contained in:
2026-09-09 22:35:54 +10:00
parent b520b862e9
commit 9b33f27d47
+5 -4
View File
@@ -18,12 +18,13 @@ from.
## Install
Each tag is published as a source zip to the `nvim-plugins` artifactapi repo,
so arti-pack installs the same way as everything it manages:
Each tag is published as a source zip under the same tag-archive path shape
arti-pack expects, so it installs the same way as everything it manages —
mirror it into your own artifact repository and fetch it from there:
```sh
curl -fsSL -o /tmp/arti-pack.zip \
https://artifactapi.k8s.syd1.au.unkin.net/api/v2/remotes/nvim-plugins/files/unkin/arti-pack/archive/refs/tags/v0.1.0.zip
https://artifacts.example.com/artifactory/nvim-plugins/unkin/arti-pack/archive/refs/tags/v0.1.0.zip
mkdir -p "${XDG_DATA_HOME:-$HOME/.local/share}/nvim/site/pack/arti-pack/start"
unzip -q /tmp/arti-pack.zip -d /tmp/arti-pack
mv /tmp/arti-pack/arti-pack-0.1.0 \
@@ -36,7 +37,7 @@ Once installed it can carry itself, since `url` bypasses the registry:
{
'unkin/arti-pack',
tag = 'v0.1.0',
url = 'https://artifactapi.k8s.syd1.au.unkin.net/api/v2/remotes/nvim-plugins/files/unkin/arti-pack/archive/refs/tags/v0.1.0.zip',
url = 'https://artifacts.example.com/artifactory/nvim-plugins/unkin/arti-pack/archive/refs/tags/v0.1.0.zip',
}
```